Known Issues with OpenShift 4.12 to 4.13 or 4.13 to 4.14 vSphere CSI Storage Migration
Historically, Kubernetes storage drivers have been delivered as “in-tree” plugins where the drivers lived and were shipped as part of the Kubernetes core code. Over the past few years, the in-tree approach has transitioned to a new standard called Container Storage Interface (CSI) where the driver’s code lives outside of Kubernetes. As a result the in-tree drivers are progressively being deprecated upstream and will be ultimately removed, and Red Hat OpenShift Container Platform is also making this transition. In order to provide a transition path to clusters that are currently using in-tree persistent volumes (PVs), a CSI migration path is offered. This process is transparent to end-users and applications (in most situations - vsphere drivers being the exception), the volumes still appear to be in-tree but the internal calls are transparently translated to CSI.
CSI migration is automatically enabled when GA, it does not require any administrator action, the process is completely transparent to both administrators and end-users. Upgraded clusters will have CSI migration automatically enabled after they upgrade to a version that supports migration. This is true for all drivers except vSphere, where we had to take a particular and unique approach on how we address the CSI migration. Please see the, Manually enabling CSI automatic migration documenation for more infomration on how to execute the vSphere CSI Storage Migration.
- Note: With OCP 4.14 the vSphere migration happens automatically. You are strongly recommended to update to at least vSphere 7.0 Update 3L or 8.0 Update 2 before upgrading to OpenShift 4.14, to avoid the currently known issues.
Providing admin-acks for upgrading
With both the 4.12 (starting with 4.12.37) to 4.13 and 4.13 to 4.14 upgrades, OpenShift Cluster Administrators will be required to provide an 'admin ack' to complete the upgrade, if you are not on vSphere versions that are recommended for CSI migration( 7.0u3l or 8.0u2). Without these 'acks' the cluster will hang (or block) the upgrade failing PreconditionChecks.
Providing admin-acks for upgrading for 4.12 to 4.13
- For more details please refer to the OpenShift documentation
$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.12-kube-126-vsphere-migration-in-4.14":"true"}}' --type=merge
Providing admin-acks for upgrading for 4.13 to 4.14
- For more details please refer to the OpenShift documentation
It is strongly recommended to upgrade your vSphere version to versions that support CSI migration(at least vSphere 7.0 Update 3L or 8.0 Update 2), because OCP-4.14 will have CSI migration enabled by default. If you upgrade your vSphere version then admin-ack below will not be necessary. However if you do wish to proceed, you may run into issues listed below.
$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.13-kube-127-vsphere-migration-in-4.14":"true"}}' --type=merge
Providing admin-acks for an EUS to EUS upgrading (4.12 to 4.14)
- For more details please refer to the OpenShift documentation
It is strongly recommended to upgrade your vSphere version to versions that support CSI migration(at least vSphere 7.0 Update 3L or 8.0 Update 2), because OCP-4.14 will have CSI migration enabled by default. If you upgrade your vSphere version then admin-ack below will not be necessary. However if you do wish to proceed, you may run into issues listed below.
$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.12-kube-126-vsphere-migration-in-4.14":"true"}}' --type=merge
$ oc -n openshift-config patch cm admin-acks --patch '{"data":{"ack-4.13-kube-127-vsphere-migration-in-4.14":"true"}}' --type=merge
Known Issues:
As is denoted, in the documentation there are some known issue that arise from possible operational situations that can cause the migration to fail; and manual interventions to need to be taken. This page denotes these issues; and where possible lists what actions you should take to correct them.
If you want to verify if you are using in-tree or csi drivers please refer to KCS 6995590 for more verification steps.
