vSphere CSI Driver does not support Kubernetes 1.22

[pennyscissors]

The vSphere CSI Driver does not support Kubernetes 1.22 due to unsupported v1beta1 CRD APIs. Support will be added at a later release (support matrix), but in the meantime users with the CSIMigrationvSphere feature enabled should be warned not to upgrade to Kubernetes 1.22 in our release notes.

Kubernetes v1.22 changelog: CSI known issues

Blocked by:

• New release image (v1.22) is not pushed to GCR kubernetes/cloud-provider-vsphere#504

[brandond]

It looks like things might work with the 1.22.2 release: https://github.com/kubernetes/cloud-provider-vsphere/releases/tag/v1.22.2

It'd be nice if they'd update that tracking issue to confirm whether or not it's fixed, although I can successfully pull gcr.io/cloud-provider-vsphere/cpi/release/manager:v1.22.2 now so I suspect things should work.

cc @pennyscissors

[deniseschannon]

Install RKE1 with k8s 1.22 and deploy vsphere charts through apps & marketplace. Check that volumes work after CSI driver is deployed.

[sirredbeard]

Dev validate and release note.

[slickwarren]

I was able to test this using 2.6.4-rc13:

• deploy downstream cluster (1cp, 1etcd, 2worker nodes) on 1.22.7-rancher1-1
• deploy cpi 100.2.0+up1.1.0 -- pass
• deploy csi 100.2.0+up2.4.1-rancher1 -- pass
• deploy a workload and mount a pv to it -- pass
• write data to the volume/check in datastore (through vsphere) -- pass

[braunsonm]

The release notes for 2.6.4 still state that vSphere does not support Kubernetes 1.22, but this was closed ahead of the release. Does this still block Kubernetes 1.22 in 2.6.4?

[phillipsj]

This was merged in and we have 1.22 support.