Move component to an appropriate upgrade order (generic) #52
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
Now that CVO only applies ordering on update, we are reorganizing the order components are applied to better align with correct upgrades. The order is: 0000_10_*: config-operator 0000_20_*: kube-apiserver 0000_25_*: kube scheduler and controller manager 0000_30_*: other apiservers: openshift and machine 0000_40_*: reserved 0000_50_*: all non-order specific components 0000_60_*: reserved 0000_70_*: disruptive node-level components: dns, sdn, multus 0000_80_*: machine operators 0000_90_*: reserved for any post-machine updates Operators in 0000_50_* should have no prefix (like 0000_70_ before). No other rules of ordering have changed.
openshift-ci-robot
added
the
size/XS
|
/lgtm |
|
/retest |
smarterclayton
added
the
approved
|
/retest Please review the full test history for this PR and help us cut down flakes. |
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.
Now that CVO only applies ordering on update, we are reorganizing
the order components are applied to better align with correct
upgrades. The order is:
0000_10_: config-operator
0000_20_: kube-apiserver
0000_25_: kube scheduler and controller manager
0000_30_: other apiservers: openshift and machine
0000_40_: reserved
0000_50_: all non-order specific components
0000_60_: reserved
0000_70_: disruptive node-level components: dns, sdn, multus
0000_80_: machine operators
0000_90_: reserved for any post-machine updates
Operators in 0000_50_* should have no prefix (like 0000_70_
before). No other rules of ordering have changed.