config checksum annotation
A hash of a ConfigMap or Secret placed in a pod template annotation, so that changing the configuration changes the template and triggers a rollout.
In more detail
Pods do not restart when their configuration changes, so this pattern makes the rollout deliberate and visible. Helm charts commonly compute the checksum when rendering. Without it, some pods can run old settings while others run new ones.
Related terms
- ConfigMap — The Kubernetes object that holds non-secret settings as key and value pairs, for pods to read as environment variables or files.
- annotation — A key-value note attached to a Kubernetes object that tools read for extra configuration.
- rollout — The controlled change of a Deployment, DaemonSet or StatefulSet from one pod template version to the next.
- hash — A short fixed-length fingerprint calculated from data, which changes completely if even one byte of the data changes.
Taught in
- ConfigMaps, Secrets And Configuration Updates — Kubernetes: Production-Grade Container Orchestration