feat: Allow the user to set the operator update strategy #450
+14
−0
Conversation
This file contains 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
kaisoz
requested review from
fcanovai,
gbartolini,
leonardoce,
mnencia,
phisco and
sxd
as code owners
Signed-off-by: Tomas Tormo <[email protected]>
kaisoz
force-pushed
the
allow-update-strategy
branch
from
fc92984 to
aa25195
Compare
itay-grudev
added
the
chart( operator )
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.
Configuring the update strategy in Helm deployments allows users to optimize rollouts for their specific needs. For example, using strategies like
RollingUpdatecan minimize downtime by updating pods incrementally, whileRecreatemight be preferable for certain scenarios where full restarts are needed to ensure consistency.This PR enables users to set the deployment update strategy via the
values.yamlfile, enhancing flexibility.