This section provides information for managing storage for TKG Service clusters. What to read next Storage Concepts for TKG Service ClustersTKG cluster workloads may require persistent storage. Refer to the information in this topic for vSphere storage concepts and considerations for TKG Service clusters. Considerations for Using Node Volume MountsYou can provision a TKG Service cluster with one or more node volume mounts. Before you do, keep in mind important considerations. Create a vSphere Storage Policy for TKG Service ClustersA 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 Application in a TKG Service ClusterStateful 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 TKG Service ClusterYou can statically create a block volume in a TKG Service cluster using an unused persistent volume claim (PVC) from Supervisor. Persistent Volume Expansion for TKG Service ClustersYou can use the Kubernetes volume expansion feature to expand a persistent block volume after its creation. TKG Service clusters support offline and online volume expansion.
