Adding a annotation flag to trigger rollout on change of cm/secrets #771
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #773
#724 This pr removed the functionality of triggering a rollout strategy on change of configmap/secrets.
But there are some cases when we want to trigger a rollout instead of just restarting the pod.
As part of this pr,
reloader.stakater.com/triggerRollout
if set totrue
will trigger a rollout strategy for that rollout. The default can be unset orfalse
, so current behaviour should continue on.Example
Setting as true