Description
templates/deployment.yaml checksums env.yaml and secrets.yaml in pod annotations but does not checksum the citadel-models ConfigMap. When modelsConfig changes via helm upgrade, the ConfigMap updates but the pod doesn't restart — leaving stale model configuration running until the pod is manually restarted.
Expected Behavior
Changing modelsConfig in values.yaml and running helm upgrade should trigger a pod rollout automatically, just like changes to env or secret values do.
Fix
Add a checksum/models annotation in templates/deployment.yaml alongside the existing checksums:
checksum/models: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }}Found During
Local testing of v0.2.1 on Docker Desktop Kubernetes.
Description
templates/deployment.yamlchecksumsenv.yamlandsecrets.yamlin pod annotations but does not checksum thecitadel-modelsConfigMap. WhenmodelsConfigchanges viahelm upgrade, the ConfigMap updates but the pod doesn't restart — leaving stale model configuration running until the pod is manually restarted.Expected Behavior
Changing
modelsConfiginvalues.yamland runninghelm upgradeshould trigger a pod rollout automatically, just like changes to env or secret values do.Fix
Add a
checksum/modelsannotation intemplates/deployment.yamlalongside the existing checksums:Found During
Local testing of v0.2.1 on Docker Desktop Kubernetes.