Atlas: ConfigMap/Secret Not Found

What this usually means

The pod spec references a ConfigMap/Secret name or key that does not exist in the namespace, or a wiring pattern that hides missing keys until runtime.

What to inspect first

Read events and the pod spec wiring (env, envFrom, volume mounts).

• Names are namespace-scoped.
• Keys are case-sensitive; one character is the difference between stable and broken.

kubectl describe pod <pod> -n <ns>
kubectl get configmap,secret -n <ns>

kubectl get pod <pod> -n <ns> -o yaml | rg -n "envFrom:|configMapKeyRef|secretKeyRef|volumes:|volumeMounts:"

Resolution guidance

Fix the governing reference, then roll once and verify convergence.

• Correct the name/key in the manifest or create the missing object intentionally.
• Avoid blind pod deletes; make sure the next pod will be better before you trigger it.
• After the fix, use rollout status and events to confirm stability.