ConfigMaps and Configuration Delivery

Baking configuration values directly into a container image means rebuilding and redeploying the image every time a setting changes, even a trivial one - so Kubernetes gives you a dedicated object, the ConfigMap, to hold non-secret configuration data (like a feature flag, a log level, or an application.yaml file) completely separately from the image itself. You can hand that data to a Pod three ways: as individual environment variables (env), as a bulk import of every key as an environment variable (envFrom), or as files inside a mounted volume (a "projected volume"). The delivery mechanism you choose has a real behavioral consequence worth understanding clearly: environment variables are captured once, at the exact moment the container process starts, and never change again for that process's lifetime - even if you update the ConfigMap five minutes later. Mounted files, by contrast, do get updated on disk automatically after a short delay, but the application itself still has to notice the file changed and reload it; Kubernetes does not restart your process for you. Because of that gap, many teams deliberately make ConfigMaps immutable (named with a version or content hash baked into the name, like app-config-v3) and treat any change as a new object entirely - this trades a small amount of extra YAML churn for the predictability of a proper, versioned rollout every time configuration changes.

Analogy: Kubernetes is a thermostat, not a remote control. You declare the temperature; independent controllers measure reality and keep acting. Debugging means finding which sensor, rule or actuator prevents convergence.

Read the object as evidence

kubectl get RESOURCE NAME -n NAMESPACE -o yaml
kubectl describe RESOURCE NAME -n NAMESPACE
kubectl get events -n NAMESPACE --sort-by=.metadata.creationTimestamp
kubectl explain RESOURCE.spec

Do not memorize these as a ritual. The first command exposes desired and observed state, the second connects conditions and events, the third supplies a timeline, and the fourth checks the server's schema. Compare what the controller was asked to do with what it reports doing. Then test the narrowest hypothesis.

Scenario: A ConfigMap is updated with a new value, and kubectl get configmap correctly shows the new content immediately - the API server did exactly what was asked. But the running Pods, which loaded that value into an environment variable at startup, keep using the old value indefinitely, because nothing about updating a ConfigMap object causes an already-running process to restart or re-read anything. The API state and the process's in-memory state are simply two different things. Either trigger a proper rollout (so new Pods start fresh with the new value) or design the application to actively watch and reload its mounted configuration file.

Make configuration revision visible

Environment variables are captured when the container starts. Projected ConfigMap files update asynchronously through the kubelet, but a process must reread them and subPath mounts do not receive normal projection updates. For predictable releases, name immutable ConfigMaps by content version or annotate the Pod template with a checksum so a change creates a rollout. Inspect effective values from the Pod spec and mounted files, not only the source object.

Scenario: Half the replicas reload a file while half cache it, producing inconsistent behavior behind one Service. Choose an atomic reload contract or roll every replica to a named configuration revision.
Warning: ConfigMap size and API storage are not a substitute for artifact storage. Package large assets in images or purpose-built stores.

Production reasoning

Ask four questions: Who owns this object? What dependency must become ready next? Which controller reports the blocking condition? What evidence would disprove my current theory? This prevents symptom-driven changes. Record the context, namespace, object generation, image digest and recent rollout before mutation; a recreated Pod may erase the evidence you needed.

Warning: Running is not the same as ready, healthy, durable or correct. Kubernetes status is layered. Confirm the application-level outcome as well as the object state.
Goal: Put this model into practice in the Kubernetes lab configmap-secret-mount. Open /labs/kubernetes, choose configmap-secret-mount, predict the failure path before changing anything, then use the simulator's check command to validate the finished state.

Deliberate practice

Before the lab, write the expected object relationship and the first three commands you will run. Afterward, explain why the fix converged and name one tempting change that would only mask the symptom. Repeat using an explicit namespace and a structured output format. This prediction-observation-explanation loop is what turns command familiarity into production judgment.

45-minute investigation

  1. Map (5 min): draw the owner-to-child chain and mark every namespace, selector, identity and dependency involved.
  2. Predict (5 min): write one expected status condition, one likely event and one log or metric signal before opening the lab.
  3. Observe (10 min): collect YAML, describe output and ordered events. Do not mutate state. Record which observation disproves your first theory.
  4. Repair (15 min): make the smallest declarative correction, watch the responsible controller converge, and verify the user-facing path rather than stopping at Running.
  5. Stress (10 min): change one relevant constraint - replica count, label, readiness, resource value or placement rule - predict the outcome, observe it, then restore the known-good declaration.
Tip: Keep a short incident note with symptom, evidence, hypothesis, change, result. Across four sections this produces a reusable runbook instead of a pile of remembered commands.