Enable DaemonSet rolling-update in manifests #1506
Merged
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
caseydavenport
added
the
release-note-required
robbrockbank
approved these changes
Dec 14, 2017
|
And I guess it's sufficient for these additions to be in the new manifest, right? So specifically, when upgrading from a 2.6.4 manifest to 3.0.0, it is correct to say that we don't need these additions in the 2.6.4 manifest? |
|
@neiljerram yep that's right |
caseydavenport
added a commit
that referenced
this pull request
Dec 14, 2021
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.
Description
Fixes #1272
This enables rolling update by default in the DaemonSet, which means users can now simply apply the new manifest and Calico will be upgraded.
Todos
Release Note