Kubernetes persistent data is managed through Persistent Volumes (PV) and Persistent Volume Claims (PVC). The platform can automatically configure an NFS volume provisioner for the Kubernetes Cluster so a new persistent volume is created automatically whenever an application submits a PVC.
Persistent Volume (PV)
Storage provisioned for Kubernetes with a lifecycle that is independent of any individual pod.
Persistent Volume Claim (PVC)
A workload request for persistent storage with a specific size and access mode.
Dynamic Provisioning
Automatically creates matching persistent volumes when PVCs are submitted.
StorageClass
Defines how Kubernetes should dynamically provision storage for a PVC.
Kubernetes separates persistent storage from individual pods through the PV and PVC model.
PV
Represents the storage resource available to Kubernetes. Its lifecycle does not depend on a particular pod.
PVC
Describes how much storage an application needs and the required access mode.
Without dynamic provisioning, an administrator normally has to prepare suitable Persistent Volumes and StorageClass settings before applications can claim the required storage.
Automatic NFS Volume Provisioning
The Kubernetes Cluster installer can automatically attach dedicated NFS storage with dynamic volume provisioning.
Enable dedicated NFS storage with dynamic volume provisioning during Kubernetes Cluster installation.
With the provisioner enabled, each new PVC automatically triggers creation of a matching Persistent Volume. This removes the need to create PVs manually for the desired access mode or StorageClass.
Main benefit: Applications can request persistent storage through PVCs while the platform-managed provisioner creates the underlying volumes automatically.
Dedicated Shared Storage Container
The platform implementation of the Kubernetes NFS volume provisioner uses a dedicated Shared Storage Container.
The storage node is visible directly in the Kubernetes environment topology.
Kubernetes Persistent Volumes created by the provisioner use this storage backend.
The storage container is separate from application pods, which helps keep persistent data independent of pod lifecycle.
The dedicated Shared Storage Container holds dynamically provisioned Kubernetes data.
Default StorageClass
The Kubernetes Cluster uses jelastic-dynamic-volume as its default StorageClass for the built-in dynamic volume provisioner.
Because this StorageClass is configured as the default, PVCs can use dynamic provisioning without requiring administrators to specify or manually configure a separate storage class for standard use cases.
Persistent Data Location
All data created by the default Kubernetes volume provisioner is stored in the following directory on the Shared Storage Container:
Storage path:/data
This central storage location is used for the persistent volumes dynamically allocated to Kubernetes applications.
Volume provisioner summary: Enable dedicated NFS storage, let applications request storage through PVCs, and allow the default jelastic-dynamic-volume StorageClass to automatically create matching Persistent Volumes on the Shared Storage Container.
