Repository navigation
Deployments require manual rollout when configmap and secret change #116
Description
I have noticed that when making updated to the values that affect the ConfigMap and/or Secret the deployment needs to be rollout restarted
kubectl rollout restart deployment/
If the pod spec contained the sha hash of the configmap and secret it would automatically rollout.
https://v3.helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments
kind: Deployment
spec:
template:
metadata:
annotations:
checksum/configmap: {{ include (print $.Template.BasePath "/config.yaml") . | sha256sum }}
checksum/secret: {{ include (print $.Template.BasePath "/secrets.yaml") . | sha256sum }}
Activity
levkk commentedon Jul 6, 2026
This is by design! Most config options can be reloaded online without pod restarts.
JeffCook-Alethea commentedon Jul 6, 2026
Should there be a log entry to say the config was reloaded?
JeffCook-Alethea commentedon Jul 6, 2026
I just changed a user password and the new password didn't work until I restarted the pods.
levkk commentedon Jul 6, 2026
Check this out: https://docs.pgdog.dev/configuration/#hot-reload
JeffCook-Alethea commentedon Jul 6, 2026
I don't see
checkoutTimeoutin the values.yaml file?I had tried for a few minutes before I restarted the pod.
I'm using
v0.68levkk commentedon Jul 6, 2026
Seems to be there: https://github.com/search?q=repo%3Apgdogdev%2Fhelm%20checkoutTimeout&type=code.
values.yamldoesn't need to have all defaults - pgdog has them already, and the chart doesn't need to configure all settings, just the ones you care about.Kube is odd, it takes a few minutes to sync the
ConfigMapto the pods. You need to monitor the disk for changes, unfortunately, and only once you see the new config loaded, you can hit reload. It's kinda annoying, but you can make it work with a bash / python script.FWIW, you can fork the chart and make it redeploy on config changes. It's not in
mainbecause it's not something most people would want because it breaks app --> pgdog connections, which is noisy / can cause downtime.We also built a monitor / automatic reload trigger into the enterprise edition, if you're curious: https://docs.pgdog.dev/enterprise_edition/
JeffCook-Alethea commentedon Jul 7, 2026
I also set
readWriteSplitin the values file. After 5 minutes it was still not respecting the new setting. I bounced the pod and it started working.