This section provides information for managing storage for TKG clusters on Supervisor. What to read next Storage Considerations for TKG Clusters on SupervisorTKG cluster workloads may require persistent storage. Refer to the information in this topic for vSphere storage concepts and considerations for TKG clusters on Supervisor. Considerations for Using Node Volume MountsYou can provision a TKG cluster on Supervisor with one or more node volume mounts. Before you do, keep in mind important considerations. Create a vSphere Storage Policy for TKG Clusters on SupervisorA vSphere storage policy that you assign to a vSphere Namespace is converted to a Kubernetes storage class. You use this storage class to control how TKG cluster nodes and persistent volumes are placed within vSphere datastores. A vSphere storage policy for vSphere Zones needs to be compatible with storage across all vSphere clusters comprising the Zonal topology. Provision a Dynamic Persistent Volume for a Stateful ApplicationStateful applications, for example databases, save data between sessions and require persistent storage to store the data. The retained data is called the application's state. You can later retrieve the data and use it in the next session. Kubernetes offers persistent volumes as objects capable of retaining their state and data. Provision a Static Persistent Volume in a Tanzu Kubernetes Grid ClusterYou can statically create a block volume in a Tanzu Kubernetes Grid cluster using an unused persistent volume claim (PVC) from the Supervisor. Persistent Volume Expansion for TKG Clusters on SupervisorYou can use the Kubernetes volume expansion feature to expand a persistent block volume after its creation. Tanzu Kubernetes Grid clusters support offline and online volume expansion.