Skip to content
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

[ENHANCE]Support triggering a rollout strategy or current behaviour of pod restart on change. #773

Open
wololowarrior opened this issue Oct 22, 2024 · 0 comments · May be fixed by #771
Open
Labels
kind/enhancement New feature or request

Comments

@wololowarrior
Copy link

Is your feature request related to a problem? Please describe.
There are some cases when we need to trigger a rollout strategy instead of just restarting the pods.
#724 This pr removed the functionality of triggering a rollout strategy on change of configmap/secrets.

Describe the solution you'd like
Adding a new annotation to the rollout will trigger a rollout strategy for that rollout. The default can be unset or false, so current behaviour should continue on.

Describe alternatives you've considered
Current behaviour only triggers restarting of pods.

Alt can be along the same lines:

  1. Add a helm value that can allow us to switch bw behaviours, but that is cluster wide setting and not desirable.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant