Starting with VMware Cloud Director Container Service Extension 3.1.3, you can optionally configure a default storage class when you create a Tanzu Kubernetes Grid cluster, and this storage class is used by default for the creation of any persistent volumes. This feature automates steps for the tenant users to manage the Tanzu Kubernetes Grid cluster for their developers in their organization.

In the Kubernetes Container Clusters UI plug-in in VMware Cloud Director, the Create Default Storage Class toggle is activated by default. You can deactivate the toggle to opt out of the function.

You can configure the following fields in a default storage class:

Table 1. Default Storage Class Configuration Fields
Configuration field Description
VMware Cloud Director Storage Profile Name Select one of the available VMware Cloud Director storage profiles.
Storage Class Name The name of the default Kubernetes storage class. This field can be any user-specified name with the following constraints, based on Kubernetes requirements:
  • Contain a maximum of 63 characters
  • Contain only lowercase alphanumeric characters or hyphens
  • Start with an alphabetic character
  • End with an alphanumeric character
Reclaim Policy
  • Delete policy: This policy is set by default. This policy deletes the PersistentVolume object when the PersistentVolumeClaim is deleted.
  • Retain policy: This policy does not delete the volume when the PersistentVolumeClaim is deleted, and the volume can be reclaimed manually.
Filesystem
  • xfs
  • ext4: This is the default filesystem used for the storage class.

For instructions on how to configure a default storage class in the Kubernetes Container Clusters UI plug-in in VMware Cloud Director, see Create a Tanzu Kubernetes Grid Cluster.