You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Nautobot Helm Deployment maintainer I am having inconsistent deployments depending on what values I change using helm upgrade. It isn't breaking but it can be annoying.
I want to make sure I understand the problem correctly. If you change something that only updates a ConfigMap, your Deployments are not restarted, and a new environmental variable is not injected into pods. Is that correct?
I want to make sure I understand the problem correctly. If you change something that only updates a ConfigMap, your Deployments are not restarted, and a new environmental variable is not injected into pods. Is that correct?
As a Nautobot Helm Deployment maintainer I am having inconsistent deployments depending on what values I change using
helm upgrade
. It isn't breaking but it can be annoying.Found a recommendation from the Helm Docs:
https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments
Seems like it would be straight forward to implement in this chart.
I couldn't find anywhere where it was utilizing this in any of the deployment charts eg.
helm-charts/charts/nautobot/templates/celery-deployment.yaml
Line 8 in 4241333
But maybe it isn't needed 🤷🏻.
Submitting this for some extra 👀
The text was updated successfully, but these errors were encountered: