Move component to an appropriate upgrade order (network) #158
Conversation
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
How does that work exactly? Is CNO special-cased or something? (To still be brought up early at install time) |
|
Everything at install time comes up all at once. There is no order during install. Everyone races to get up, backs off if they can't, and waits if necessary. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, smarterclayton The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
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.