Use checksum/config to automagically roll deployments on ConfigMap Changes

[ak-a]

Make Argo Workflows Deployment Restart on Config change

Add an annotation to the Argo Workflows helm chart as documented:
https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments

Use Cases

Deploying Argo Workflows using Argo CD would then automatically restart the Deployment as the deployment changes if the Config changes. Simpler than having a ConfigMap watch which is buggy on some Kubernetes versions and has an overhead on the cluster.

---

Message from the maintainers:

Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.

[agilgur5]

Add an annotation to the Argo Workflows helm chart

There are no Helm Charts in this repo. Not sure if you meant to post this in https://github.com/argoproj/argo-helm?

automatically restart the Deployment as the deployment changes if the Config changes. Simpler than having a ConfigMap watch

It is simpler and you can certainly use that as a workaround. It is recommended for the Server even as it has no hot reloading feature yet: #10970.

However the Controller ConfigMap watch feature is different from this. It changes the configuration in-memory without needing a restart (or rolling deploy).

As such, if it were to be added to argo-helm, the feature should be optional, as the Controller already has a built-in feature for that that does not require a restart.

a ConfigMap watch which is buggy on some Kubernetes versions

It sounds like you're referring to #11657, which is slated to be fixed soon.

[ak-a]

Thanks @agilgur5 - I have raised the issue in the helm repo. I am hoping to find time to contribute a possible patch myself.