The Kubernetes Cluster provides an automated NFS-based volume provisioner as its standard persistent-storage option. This is the recommended approach for most Kubernetes deployments because it is integrated directly into the cluster installation flow and supports dynamic volume provisioning.
Recommended Option
Use the built-in NFS volume provisioner when the standard Kubernetes storage model meets application requirements.
Custom Storage
Other storage backends can be integrated when the default NFS solution does not meet the workload’s needs.
The standard automated storage backend for the Kubernetes Cluster is the built-in NFS volume provisioner. It can be enabled directly from the Kubernetes package installation wizard.
Enable the built-in NFS storage option during Kubernetes Cluster installation.
When enabled, this storage backend works together with the Kubernetes volume provisioner to dynamically create Persistent Volumes for application Persistent Volume Claims.
Recommended Approach
Recommendation: Use the built-in NFS volume provisioner whenever it satisfies the application’s storage requirements. It is the storage option designed for automated deployment and integration with the Kubernetes Cluster package.
Storage can be selected during Kubernetes Cluster installation.
The provisioner integrates with Kubernetes Persistent Volume Claims.
Dynamic provisioning reduces the need to create Persistent Volumes manually.
The storage workflow is already integrated into the standard cluster package.
Using a Custom Storage Backend
If the standard NFS storage does not satisfy the application’s technical requirements, another storage backend can be integrated with the Kubernetes Cluster.
Custom storage is not provided through the same automated installation workflow as the default NFS provisioner. The integration method depends on the selected storage technology and Kubernetes requirements.
The source documentation recommends contacting platform support to discuss available storage options and obtain assistance with custom implementation.
Step 1 — Define Requirements
Determine the required capacity, access mode, performance, replication, availability, and storage lifecycle.
Step 2 — Select Backend
Choose a Kubernetes-compatible storage solution that meets the workload requirements.
Step 3 — Integrate with Kubernetes
Configure the selected backend, StorageClass, Persistent Volumes, or CSI/provisioning components as required by that storage technology.
Step 4 — Validate
Confirm that application PVCs can bind correctly and that the required access modes and data-persistence behavior work as expected.
Important: The exact custom-storage configuration is backend-specific. Follow the requirements of the selected storage provider and Kubernetes version rather than treating the built-in NFS configuration as a universal template.
Gluster-Based Storage Note
The source documentation mentions a Gluster-based storage option as a planned future addition to Kubernetes package versions.
Because storage features can change between Kubernetes package releases, review the current Kubernetes Cluster version documentation before assuming that a specific additional storage option is available.
Custom storage summary: Prefer the integrated NFS volume provisioner for standard deployments. If NFS does not meet the workload requirements, a different storage backend can be used, but it requires a custom Kubernetes integration appropriate to that storage technology.
