A Pod in the inspections namespace mounts a volume from ConfigMap app-settings, but the ConfigMap was created only in default. What is the most likely result?
Select an answer to reveal the explanation.
Short Explanation
ConfigMaps are like office binders that stay on their own floor—namespaces don't share them. If the Pod runs in inspections but the ConfigMap lives only in default, the mount reference misses. Create or copy the ConfigMap in the same namespace as the Pod.
Full Explanation
ConfigMaps are namespaced resources. A Pod can only mount or reference a ConfigMap that exists in its own namespace; the control plane does not auto-copy ConfigMaps across namespaces. Missing ConfigMap volume references typically leave the Pod unable to start correctly (CreateContainerConfigError or similar), not silently empty with healthy Ready. Cross-namespace ConfigMap mounts via kube-proxy are not a Kubernetes feature.