[WIP] Two stage update hypershift IC rebase#1860
[WIP] Two stage update hypershift IC rebase#1860flavio-fernandes wants to merge 9 commits intoopenshift:masterfrom
Conversation
- Determine OVN interconnect zone mode by inspecting an (optional) configMap; apply the desired zone mode. - upgrade from non-IC to IC OVN-K by going through an intermediate step with 1-zone - Switch from IC single zone to IC multizone (as in upgrades) and back (not fully supported yet, for internal use only) Avoid clashes between single-zone ovnkube-master (using ports 9102, 9641, 9642, 29102) and multizone ovnkube-node (initially using ports 9103, 9105, 9102, 29102, 29103) during upgrade from 4.13 and avoid using ports reserved for the storage components, as described in https://github.com/openshift/enhancements/blob/master/dev-guide/host-port-registry.md This caused the storage operator to never be available after installation of or upgrade to 4.14. In multizone ovnkube-node let's now have: - 9103, 9105, 29103 (which don't collide with single-zone ovnkube-master) - 9112, 9112 9113, 29113 so as to not collide with single-zone ovnkube-master Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
In the very last step of the 2-phase upgrade to OVN interconnect, we remove the IC configmap. At this point, SetFromPods from pod_status.go won't be called any more, because all changes to the daemonsets have been processed. Patch the ovnk master daemonset with a dummy annotation to trigger status recalculation. TODO: find a better way to run SetFromPods instead of updating ovnk master annotations Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
Beware: this goes with https://github.com/openshift/ovn-kubernetes/pull/1727/commits Signed-off-by: Riccardo Ravaioli <rravaiol@redhat.com>
here I rename the yaml files and change them to work for hypershift-IC (cherry picked from commit 7b78d2b)
The major difference between managed and self hosted IC upgrade is the stateful set on the master side. patch the update so the commit works for this too. HACK to get the stateful set updated was to remove it when safe to do so in order to allow the CNO to create a version updated as we need to in phase 2 (cherry picked from commit 2f12a1d)
…troller (cherry picked from commit fa71de3)
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: flavio-fernandes The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@flavio-fernandes: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
| @@ -393,8 +393,15 @@ func renderOVNKubernetes(conf *operv1.NetworkSpec, bootstrapResult *bootstrap.Bo | |||
| manifestDirs = append(manifestDirs, filepath.Join(manifestDir, "network/ovn-kubernetes/common")) | |||
|
|
|||
| if bootstrapResult.OVN.OVNKubernetesConfig.HyperShiftConfig.Enabled { | |||
|
PR needs rebase. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
no longer needed see #1874 |
|
@flavio-fernandes: Closed this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
This combines ricky-rav's PR #1838 and
JacobTanenbaum's PR #1857
It should be used with latest ovnk8's downstream to upgrade from 4.13 to 4.14 in Hypershift deployments.