v2.5.0

Notable Changes

• Support for Kubernetes version 1.23
• Decouple vSphere CSI from vSphere CPI - vSphere CSI driver no longer depends upon the Kubernetes Node ProviderID set by vSphere CPI for its operations. This provides the ability to use custom CPI along with vSphere CSI driver.
• Snapshot feature support for block volumes - Refer to this link for more detail.
• Expose metrics for prometheus monitoring - Refer to this link for more detail.

Release Note



Refer to https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/2.5/rn/vmware-vsphere-container-storage-plugin-25-release-notes/index.html for more details

v2.3.1

New Features

There is no new feature released in v2.3.1.
v2.3.1 is the patch release to fix issues observed in the v2.3.0 release for in-tree vSphere volume migration to vSphere CSI.

Notable Changes

• Prevent calling register volume in parallel for the same VMDK. See #1398
• Fix issues related to volume path parsing during migration of in-tree vSphere volumes to vSphere CSI. See #1447

Release note

https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/2.3/rn/vmware-vsphere-container-storage-plugin-23-release-notes/index.html

v2.4.1

Notable Changes

• This patch release enables offline resize in vSphere 6.7 P06 and any future patches on vSphere 6.7 release. See #1437.
• Fix issues related to volume path parsing during migration of in-tree (VCP) volumes to vSphere Container Storage Plug-in. See #1447
• This patch enables you to use volume topology feature with vSphere 6.7 P06 and any future patches on vSphere 6.7 release.
• If you use the Beta topology feature, this version enables you to upgrade to the latest vSphere Container Storage Plug-in release. Refer to upgrade considerations and guidelines.

Release Note



Refer to https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/2.4/rn/vmware-vsphere-container-storage-plugin-24-release-notes/index.html for more details

v2.4.0

Notable Changes

• Performance and resiliency improvements.

• Volume topology support for block volumes.

  • Warning:
    • If you use the Beta topology feature in your current version of vSphere Container Storage Plug-in, do not upgrade to version 2.4.0. Upgrade to the patch version 2.4.1.
    • If you use the Beta topology feature with the in-tree vSphere Cloud Provider, do not migrate to vSphere Container Storage Plug-in version 2.4.0. Instead, you can directly upgrade to version 2.4.1 and above, as long as you are using Kubernetes version less than 1.22.
    • If you are not using the Beta topology feature, you can safely upgrade to vSphere Container Storage Plug-in version 2.4.0.
      Volume topology GA support for block volumes is available only in greenfield deployments.

• Support for Kubernetes version 1.22.

• Enhanced the idempotency handling logic of vSphere Container Storage Plug-in in the following scenarios:

  • Restarts of vSphere Container Storage Plug-in during in-flight CreateVolume operations will not result in the creation of an orphan volume on the datastore.
  • In case of multi-master setups with multiple vSphere Container Storage Plug-in controller replicas, a change of leader during an in-flight CreateVolume operation will not result in the creation of an orphan volume on the datastore.

• Windows node support is added as an Alpha feature.

• Volume snapshot support is added as an Alpha feature.

Documentation



Refer to https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/index.html for more details

v2.2.2

New Features

There is no new feature released in v2.2.2.
v2.2.2 is the patch release to fix issues observed in v2.2.1 release.

Notable Changes

• Prevent vSAN file share volumes (RWM Volume) on the node from becoming inaccessible (#1217 , @divyenpatel )
• Prevent syncer from crashing when volumes are migrated from VCP (#1013 , @chethanv28 )
• Avoid storage class creation using VCP storage class parameter DatastoreMigrationParam (#1077 , @chethanv28 )

v2.1.2

New Features

There is no new feature released in v2.1.2.
v2.1.2 is the patch release to fix issues observed in v2.1.1 release.

Notable Changes

• Prevent vSAN file share volumes (RWM Volume) on the node from becoming inaccessible (#1217 , @divyenpatel )

v2.0.2

New Features

There is no new feature released in v2.0.2.
v2.0.2 is the patch release to fix issues observed in v2.0.1 release.

Notable Changes

• Prevent vSAN file share volumes (RWM Volume) on the node from becoming inaccessible (#1217 , @divyenpatel )

v2.3.0

New Features

• XFS Filesystem support as an Alpha feature. Volumes can be provisioned by specifying xfs as the csi.storage.k8s.io/fstype in the Storage Class.
• Raw Block volume support as an Alpha feature. Visit the Raw Block Volumes documentation for more details.

Notable Changes

• Node Driver DaemonSet runs with hostNetwork. Refer to (#1217) for more detail.

• Ability to set the maximum volumes that can be attached to a Node VM. This can be modified in the CSI 2.3 deployment manifest.

• Upgrade CSI driver base image to Photon 4.0. (#866)

• Modifications in ControllerUnpublishVolume error handling (#840):

  • If the Node VM is deleted from the vCenter inventory, the detach operation will be marked as successful.
  • If a NotFound fault is returned by CNS, the VM devices are checked to ensure the volume is not attached to a Node VM.

• Bug fixes

  • Disable volume length check. (#801)
  • Set volume health annotation to Inaccessible if it is not set by SPBM as it implies volume does not exist. (#852)
  • Set volume health annotation to Inaccessible when PVC not found in CNS. (#944)
  • Prevent incorrect reloading of Virtual Center configuration in CSI Syncer when credentials are not changed. (#967)
  • Prevent syncer from crashing when volumes are migrated from VCP. (#1013)
  • Reset Volume Manager during reload config when user or ca-file is updated. (#1043)

Refer to https://vsphere-csi-driver.sigs.k8s.io/releases/v2.3.0.html for more detail

v2.2.1

New Features

There is no new feature released in v2.2.1.
v2.2.1 is the patch release to fix the critical issue observed in v2.2.0 release.

Notable Changes

• Fixed detach volume error handling (#665, @divyenpatel )

v2.2.0

New Feature

• Online Volume Expansion. Refer to Volume Expansion documentation for detail.

Notable Changes

• Added support for running vSphere CSI driver on VMware Cloud™ on AWS (VMC). VMC will only support block volume for now.
• Datastore privilege check to filter out shared datastores which do not have Datastore.FileManagement privilege. Refer to notes provided for CNS-DATASTORE role at vSphere Roles and Privileges
• Telemetry collection support using cluster-distribution field in the vSphere Config Secret. Refer to notes provided for cluster-distribution in vSphere configuration secret.
• Bug fixes
  • Fixed recreating static file share volume with the same PV name. (#546, @chethanv28)
  • Fixed metadata syncer to disallow deleting volume physically from the datastore when PV is deleted by user. (#568, @chethanv28)
  • Fixed VCP to CSI Migration to support datastore path in the volume handle. (#643, @chethanv28)
  • Fixed CSI full sync not registering volumes and was failing with Duplicated entity for each entity type in one cluster. (#671, @lipingxue)
  • Fixed volume provisioning when empty datacenter is present in the vCenter inventory. (#690, @shalini-b)

Refer to https://vsphere-csi-driver.sigs.k8s.io/releases/v2.2.0.html for more detail