Update command #24
Open
Update command #24
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updates a cluster by replacing all of the pods in that cluster with. The existing cluster is determined by the cluster name in the YAML definition together with the specified namespace. If the cluster does not exist, no action is taken. If a cluster with the appropriate name exists, then all of its pods are killed and replaced by new ones that are deployed using the provided YAML definition. I.e. the cluster size does not change after the update is completed.
Rolling updates (i.e. pods are replaced one by one) are supported via the --rolling switch. With rolling updates, it is also possible to specify a wait time between pod updates (see the -w parameter).
By default, new pods are deployed before old ones are killed. It is possible to kill old pods first vie the --kill_first switch.
This tool supports optional output in JSON format for 3rd-party integration via the -j switch.