search

BCDevOps / developer-experience

This repository is used to track all work for the BCGov Platform Services Team (This includes work for: 1. Platform Experience, 2. Developer Experience 3. Platform Operations/OCP 3)
Apache License 2.0
8 stars 17 forks source link

NSX - Upgrade ncp in KLAB2 and EMERALD to v4.2.1 #5241

Open wmhutchison opened 1 week ago

wmhutchison commented 1 week ago

Describe the issue A version of ncp which supports upgrading to Openshift 4.16 is now available. Investigate and if no technical blockers exist, pursue upgrading ncp to this version in KLAB2 and EMERALD.

Additional context Link to ncp release notes.

How does this benefit the users of our platform? Newer software supporting allowing NSX clusters to upgrade via EUS to OCP 4.16.

Definition of done

wmhutchison commented 1 week ago

FYI, latest ako for AVI currently supports up to OCP 4.15: https://docs.vmware.com/en/VMware-Avi-Load-Balancer/1.12/Avi-Kubernetes-Operator-Release-Notes/GUID-D2E95B86-A46A-48AD-9A1D-01115BD58D41.html

wmhutchison commented 3 days ago

Can't check release notes page, since it's currently broke, both what's linked in this ticket and what Google finds, will re-check later.

Just finished uploading new images to Artifactory. Looking through the big zip file to see if the vendor has updated manifests we should be using for things like Deployment versus DeploymentConfigs.

wmhutchison commented 2 days ago

Vendor release notes link works again. The ncp version question supports the range of OCP 4.14 - 4.16 which covers us both for current version and unblocks us from future OCP 4.16 upgrade work.

Will need to discuss with VMWare team since it looks like this new ncp release is not compatible with the current version of NSX, thus will need an NSX upgrade first. Will ask VMWare what plans they have for NSX upgrades, and check versions of ncp available between current version and newest version to see if there's one which spans current and future NSX versions.

wmhutchison commented 1 day ago

NSX is going to be upgraded from v3.2.3 to v3.2.4.1. The current ncp will not suffice for that and the proposed original ncp version is too new. Thus an intermediate version of ncp will be required and also upgraded/applied at the same time as when this NSX upgrade is to be applied.

Thus update this ticket to reflect we're pushing for an upgrade to ncp v4.1.2.2 instead which will weather us through the NSX planned upgrade. Once that's done (NSX upgrade and ncp to v4.1.2.2), we'll be able to freely plan the OCP 4.16 upgrade along with ncp v4.2.1 (or newer version if applicable) when we're ready for that.

wmhutchison commented 1 day ago

I still want this ticket, so going to Backlog it, create a new ticket for aligning with NSX upgrade work, and make this one dependent on the new ticket.