k8s-external-secrets-troubleshooting
External Secrets troubleshooting
Find out why External Secrets Operator (ESO) does not create or update a Secret, and propose a fix. Read first, ask before changing. Run the investigation commands freely. Run a command under an "Ask first" line only after the user approves that exact command; if your credentials do not allow it, give it to the user to run. Never run a "Proposed fix"; hand it to the user.
An ExternalSecret says which keys to fetch from an external store and which
Kubernetes Secret to write (spec.target). It uses a SecretStore (one namespace) or
ClusterSecretStore (any allowed namespace) that holds the provider configuration (a
cloud secret manager, Vault, and others). The ESO controller syncs on
spec.refreshInterval and reports the result on the ExternalSecret's Ready condition.
Never read Secrets, here least of all: not the target Secret ESO writes, not the provider credentials a store references, not the webhook's certificate. You can tell whether a sync worked from the ExternalSecret's status and events. If the user wants to check a value, they look at it themselves.