Kubernetes - StorageClasses
no-provisioner
if a PVC
is created using this StorageClass
:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: local-disks
provisioner: kubernetes.io/no-provisioner
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer
When you use a storage class with the no-provisioner
attribute, it means that the storage resources are expected to be pre-provisioned, and Kubernetes won’t dynamically provision storage for you. Instead, you need to manually create the PV
and ensure it meets the requirements specified in the PVC
.
Usage:
- HostPath volumes: Directly mount local directories from the node onto Pods, offering high performance and low latency.
- Pre-provisioned PVs: Use existing storage resources on NAS/SAN systems by manually creating PVs and assigning them the
kubernetes.io/no-provisioner
class.
LVP: local volume provisioner
Static provisioner of local volumes: https://github.com/kubernetes-sigs/sig-storage-local-static-provisioner