tezvyn:

How mounted ConfigMap updates propagate to pods

Source: interviewintermediate

WHAT IT TESTS: ConfigMap volume update semantics. OUTLINE: kubelet refreshes mounted files within roughly a sync period via an atomic symlink swap, but the app must reload on its own; env-var injection never updates.

WHAT IT TESTS: the gap between file update and application reload. ANSWER OUTLINE: when mounted as a volume, the kubelet periodically syncs the ConfigMap and atomically swaps a symlinked directory so the files reflect the new data, typically within about a minute plus cache delay. But the running application does not magically re-read them; it must watch the files or be signaled to reload. Subpath mounts and env-var injection do not update at all without a restart. RED FLAG: assuming the process auto-reloads.

Read the original → interview

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.

How mounted ConfigMap updates propagate to pods · Tezvyn