Epic Goal

• The goal of this epic is to upgrade all OpenShift and Kubernetes components that WMCO uses to v1.27 which will keep it on par with rest of the OpenShift components and the underlying cluster version.

Why is this important?

• Uncover any possible issues with the openshift/kubernetes rebase before it merges.
• WMCO continues using the latest kubernetes/OpenShift libraries and the kubelet, kube-proxy components.
• WMCO e2e CI jobs pass on each of the supported platform with the updated components.

Acceptance Criteria

• All stories in this epic must be completed.
• Go version is upgraded for WMCO and WMCB components.
• sdn-4.14 branch is created by the SDN team for using latest kube-proxy component.
• CI is running successfully with the upgraded components against the 4.14/master branch.
• Windows nodes must use the same kubelet version as the linux nodes in the cluster.

Dependencies (internal and external)

1. ART team creating the go 1.20 image for upgrade to go 1.20.
2. OpenShift/kubernetes repository downstream rebase PR merge.
3. SDN team for creating the new sdn-4.14 branch.

Open questions::

1. Do we need a checklist for future upgrades as an outcome of this epic?-> yes, updated below.

Done Checklist

• Step 1 - Upgrade go version to match rest of the OpenShift and Kubernetes upgraded components.
• Step 2 - Upgrade Kubernetes client and controller-runtime dependencies (can be done in parallel with step 3)
• Step 3 - Upgrade OpenShift client and API dependencies
• Step 4 - Update kubelet and kube-proxy submodules in WMCO repository
• Step 5 - Engage SDN team to create new branch for kube-proxy submodule (can be done in parallel with above steps)
• Step 6 - CI is running successfully with the upgraded components and libraries against the master branch.