-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] replace helm-rollout-restarter method with helm best practice to restart pods on configmap changes #3403
Labels
Comments
This was referenced May 10, 2024
Closed
I turned on debug logging on the cluster-controller. Here is the log from my most recent attempt to get this to work.
|
I do see this in the logs when its not trying to implement cluster turndown:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement
pods should get restarted during deployment when configmaps change. However, the current approach with "helm-rollout-restarter" always restarts the pods when "helm template" is running which results in a restart whenever argocd recognizes git commits in the gitops repo. There is a feature to disable helm-rollout-restarter introduced with #3324. however, then pods never ever get restarted when configmaps change.
Solution Description
Use the helm best practice https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments which is also used in loki: https://github.com/grafana/loki/blob/5ada92b190c671055bb09ca2dd234b6bac49289e/production/helm/loki/templates/admin-api/deployment-admin-api.yaml#L35
Alternatives
No response
Additional Context
No response
Troubleshooting
The text was updated successfully, but these errors were encountered: