feat(nodeAnalyzer): fix deamonset not being rollout after values changes #1533
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ProvoK
commented
Dec 15, 2023
ProvoK
force-pushed
the
vic/feat/nodeanalyzer-force-redeploy-on-configuration-changes
branch
from
12be0cf to
eaa4419
Compare
Contributor
Author
|
ready for review! |
mavimo
requested changes
Dec 15, 2023
mavimo
requested changes
Dec 15, 2023
mavimo
approved these changes
Dec 15, 2023
mavimo
force-pushed
the
vic/feat/nodeanalyzer-force-redeploy-on-configuration-changes
branch
from
7d16bd2 to
9ed862b
Compare
ProvoK
deleted the
vic/feat/nodeanalyzer-force-redeploy-on-configuration-changes
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it:
Force rollout when configmap(s)/secrets & co changes
Checklist