This repository has been archived by the owner on Jan 5, 2022. It is now read-only.
telegraf: Allow DaemonSet updateStrategy specification #109
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.
A user may want to update it.
E.g. on my Kubernetes 1.10.9 cluster the DaemonSet got created with
OnDelete
update policy for whatever reason, which gave me a hard time finding out why weren't pods getting re-deployed afterhelm upgrade
, nevertheless there was thechecksum/config
annotation update - until I found helm/helm#2735 (comment).It's even worth to consider enforcing the strategy to be
type: RollingUpdate
by default - so to align with expectations fromchecksum/config
annotation (which is hard coded ATM).