Releases: kubernetes-sigs/vsphere-csi-driver
v2.7.2
Notable Changes
This patch release includes a fix for the issue where the cached session gets logged out due to a race condition occurring when multiple methods attempt to connect to the vCenter simultaneously. As a result, the CSI Driver fails to authenticate the session, leading to unsuccessful volume operations.
Please see #2411 , #2155 and #2157 for more detail.
Note: This issue has already been resolved in the v3.0.x releases.
Deployment files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v2.7.2/manifests/vanilla
Release Note
v3.0.1
This is the patch release to fix issues observed in the v3.0.0 release.
Notable Changes
- Fixed a bug in the CSI full sync that caused the Delete PVC operation to fail due to the deletion of the
CNSVolumeInfoCR. More information can be found at #2327 - Resolved the panic observed in the syncer container during the full sync process. The panic occurred when stale CNS Volumes were deleted when the corresponding PV was not present in the Kubernetes cluster. Refer to #2347 for more detail.
Deployment files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v3.0.1/manifests/vanilla
v2.7.1
Notable Changes
- New sidecar versions and CVE fixes. For information, see 2304.
Deployment files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v2.7.1/manifests/vanilla
Release Note
v3.0.0
Notable Changes
- Support for Kubernetes version 1.27.
- Support for Kubernetes version 1.26
- Deployment of vSphere Container Storage Plug-in across multiple vCenter Server instances.
Note: vSphere Container Storage Plug-in does not support datastores shared across vCenter Server instances. - Automatically generated cluster IDs.
- GA support for raw block volumes.
- GA support for XFS file system.
- GA support of vSphere Container Storage Plug-in for Windows.
- List Volumes API. The API returns a list of volumes along with a list of nodes that have the volumes attached. By default, Kubernetes calls the List Volumes API every minute. This interval is configurable. With the List Volumes API, Kubernetes and vCenter Server can reconcile the asynchronous states of volume-to-node attachment. This functionality can be helpful in those cases when Kubernetes shows the volume as attached to the node, but the storage infrastructure shows the sate as not attached.
Deployment files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v3.0.0/manifests/vanilla
Release Notes
v2.7.0
Notable Changes
- Support for Kubernetes version 1.25.
- Enabled feature switch for in-tree vSphere volume to CSI migration.
- Support node VM discovery when CSI controller is upgraded to v2.5.0 and above but some of the Node's Daemonsets Pods are not upgraded to v2.5.0 and above due to the upgrade process on the platform such as VMware Tanzu Kubernetes Grid Integrated Edition. Refer to #1971 and #1966 for more detail.
- Mark volume detach as success when Node VM is deleted from vCenter. Refer to #1879 for more detail.
- Enabled feature switch to allow suspending specific datastore for volume provisioning using Cloud Native Storage Manager.
Deployment files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v2.7.0/manifests/vanilla
Release Note
v2.6.2
Notable Changes
- Support node VM discovery when CSI controller is upgraded to v2.5.0 and above but some of the Node's Daemonsets Pods are not upgraded to v2.5.0 and above due to the upgrade process on the platform such as VMware Tanzu Kubernetes Grid Integrated Edition. Refer to #1971 and #1966 for more detail.
- Enabled feature switch to allow suspending specific datastore for volume provisioning using Cloud Native Storage Manager.
- Fixed CSI Unix Domain Socket endpoint URL parsing for Windows Node Daemonset Pods. Refer to #1998 for more detail.
- Fixed publishing correct Node UUID for Windows Node. Refer to #1996 for more detail.
Deployment files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v2.6.2/manifests/vanilla
v2.5.4
Notable Changes
- Support node VM discovery when CSI controller is upgraded to v2.5.0 and above but some of the Node's Daemonsets Pods are not upgraded to v2.5.0 and above due to the upgrade process on the platform such as VMware Tanzu Kubernetes Grid Integrated Edition. Refer to #1971 and #1966 for more detail.
- Enabled feature switch to allow suspending specific datastore for volume provisioning using Cloud Native Storage Manager.
- Fixed CSI Unix Domain Socket endpoint URL parsing for Windows Node Daemonset Pods. Refer to #1998 for more detail.
- Fixed publishing correct Node UUID for Windows Node. Refer to #1996 for more detail.
Deployment files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v2.5.4/manifests/vanilla
v2.6.1
Notable Changes
- Support improved idempotency feature when the vSphere CSI driver is running in a different namespace, other than
vmware-system-csi. Refer to #1946 for more detail. - Prevent re-discovering node topology upon syncer container restart. Refer to #1906 for more detail. With this fix, we can make use of Preferential Datastore feature and retain Node's topology even when Node VM moves from one availability zone to another availability zone.
- Mark volume detach as success when Node VM is deleted from vCenter. Refer to #1879 for more detail.
Deployment YAML files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v2.6.1/manifests/vanilla
v2.5.3
Notable Changes
- Support improved idempotency feature when the vSphere CSI driver is running in a different namespace, other than
vmware-system-csi. Refer to #1946 for more detail. - Prevent re-discovering node topology upon syncer container restart. Refer to #1906 for more detail.
- mark volume detach as success when Node vm is deleted from vcenter. Refer to #1879 for more detail.
Deployment YAML files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v2.5.3/manifests/vanilla
v2.4.3
Notable Changes
- Support improved idempotency feature when the vSphere CSI driver is running in a different namespace, other than
vmware-system-csi. Refer to #1946 for more detail. - Prevent re-discovering node topology upon syncer container restart. Refer to #1906 for more detail.
Deployment YAML files
https://github.com/kubernetes-sigs/vsphere-csi-driver/tree/v2.4.3/manifests/vanilla