charts/services-deployment add rollingUpdate settings (closes #144) #146
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
ianarsenault
force-pushed
the
service-deployent/rollingUpdate
branch
2 times, most recently
from
25c8cb1 to
770cf1e
Compare
fix bump chart version fix fix
ianarsenault
force-pushed
the
service-deployent/rollingUpdate
branch
from
770cf1e to
f7c4b58
Compare
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.
This PR adds in additional settings for
deployment.strategyfor whenRollingUpdateis set, you will be able to set the maxSurge and maxUnavailable settings rather than relying on defaults.