-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Controller pods must be deleted and restarted to pick up new retention policy #11194
Comments
I can confirm that the controller does not pick up new settings after at least 2 hours. |
fixed in #10218 |
can you try with |
Thanks @sarabala1979! We'll update and report back. It looks like the code changes will indeed fix the issue. |
@sarabala1979 Is there a release planned soon so we can move this fix to our production environments. I haven't tried |
It should be available in v3.4.8 |
3.4.8 is the version we are using which exhibited the problem which led to me creating this issue. I see #10218 was merged a while back, but it seems to have not fixed our issue. |
It looks like some refactoring has taken place since the above MR as the code now lives here https://github.com/argoproj/argo-workflows/blob/dc56332e6a4de71dd0ec0af9bd8a2b9686e550b4/workflow/controller/controller.go#L406C4-L406C4 and is a bit different from the original MR. |
i think this can be closed, stakater/reloader handles this |
Pre-requisites
:latest
What happened/what you expected to happen?
Using
After making a change to the helm values and redeploying, the new retention policy settings do not take effect until the controller pods are deleted. It seems the controller code should pick up the new configmap configuration automatically. Perhaps it does but not in a timely manner?
Version
3.4.8
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
We can see this from the output of `argo list`. After updating the retention policy, the behavior remains the same until the controller pods are cycled.
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: