Project challenges / verified progress
Beacon: give it somewhere to live

The engineering notebook

Move knobs outside

How does Beacon receive configuration without baking it into the image?

Loading Vault account...
Phase 2 — Define the runtime contract

Step 01 of 06

Understand the idea

The same application image can run in development and production with different settings. Kubernetes ConfigMaps hold ordinary settings; Secrets are intended for sensitive values and must still be protected with proper access controls.

CONFIG CHANGES DIFFERConfig changenew object dataMounted filekubelet refreshes volumeeventually updatesEnvironmentcopied at process startneeds restartChecksumtemplate changesrolls pods
Kubernetes can project configuration as environment variables or as files. Files can update in a mounted volume; environment variables are copied into the process at start and stay frozen.
Step 01

Key technical ideas

ConfigMaps hold ordinary configuration

A ConfigMap stores non-secret data: listen addresses, feature flags, probe intervals, target lists and file content. It is namespaced and versioned through the API server like other objects. It is not for passwords. The value is convenience and separation: one image can run in several environments because its behavior comes from mounted files or environment variables.

Secrets are base64, not encrypted by default

A Kubernetes Secret looks safer than a ConfigMap, but its data is merely base64 encoded in the manifest format. That prevents broken YAML, not disclosure. Real protection comes from API access control, encryption at rest configured on the cluster, careful logging and never committing real credentials. For this local course, use fake values only.

Environment variables do not live-update

When Kubernetes starts a container, it constructs the environment once. If the referenced ConfigMap changes later, the process environment does not change. Mounted ConfigMap volumes are different: kubelet refreshes projected files eventually, usually within about a minute. The process still has to re-read the file, so live update is not automatic application behavior.

Checksum annotations make config changes rollout deliberately

A common production pattern is to put a hash of configuration data in the Pod template annotations. When configuration changes, the annotation changes, so the Deployment sees a new Pod template and rolls Pods. Kubernetes does not calculate that checksum for you; Helm, Kustomize or a small script usually does. The point is explicit restart, not surprise magic.

A restaurant menu is a mounted file
printed menu changes on the wall
staff can read the new page
a receipt already printed does not change

Mounted files can change for future reads. Environment variables are more like the receipt: copied once at process start. Kubernetes will not edit a running process's memory because a ConfigMap changed.

ConfigMap, Secret, env and file

ChoiceBest forGotcha

ConfigMap

Non-sensitive config

Size and text shape matter

Secret

Credentials or tokens

Base64 is not encryption

Env var

Simple startup knobs

Never updates in running process

Mounted file

Config files and lists

App must re-read or restart

Checksum annotation

Controlled restarts

You must update the hash

Technical terms used at work

  • ConfigMap — A namespaced object storing non-secret key/value data or file content.

  • Secret — A namespaced object intended for sensitive values, access-controlled by the API and encoded as base64 in manifests.

  • Projection — Kubernetes making object data available inside a Pod as files or environment variables.

  • Checksum annotation — A Pod template annotation derived from config content to trigger rollouts when config changes.