Default storage providers in DKP
When deploying DKP using a supported cloud provisioner (AWS), DKP automatically configures native storage drivers for the target platform. In addition, DKP deploys a default StorageClass for dynamic persistent volume (PV) creation. The table below lists the driver and default StorageClass for each supported cloud provisioner.
Default Storage Class
When a default StorageClass is specified, persistent volume claims (PVCs) can be created without needing to specify the storage class. For instance, to request a volume using the default provisioner, create a PVC with the following:
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: my-pv-claim spec: accessModes: - ReadWriteOnce resources: requests: storage: 4Gi
To start the provisioning of a volume, launch a pod which references the PVC:
apiVersion: v1 kind: Pod ... spec: containers: ... volumeMounts: - mountPath: /data name: persistent-storage ... volumes: - name: persistent-storage persistentVolumeClaim: claimName: my-pv-claim
Multiple Storage Classes
StorageClass provisioned with DKP is acceptable for most workloads and offers a good cost to performance ratio. If your workload has different requirements, you can create additional
StorageClass types with specific configurations.
In some instances you can change the default
StorageClass. Refer to this procedure:
All default drivers implement the Container Storage Interface (CSI). The CSI provides a common abstraction to container orchestrators for interacting with storage subsystems of various types. Each driver has specific configuration parameters which effect PV provisioning. This section details the default configuration for drivers used with DKP. This section also has links to driver documentation, if further customization is required.
StorageClass parameters cannot be changed after creation. To use a different volume configuration, you must create a new
Amazon Elastic Block Store (EBS) CSI Driver
DKP EBS default
kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: annotations: storageclass.kubernetes.io/is-default-class: "true" # This tells kubernetes to make this the default storage class name: ebs-sc provisioner: ebs.csi.aws.com reclaimPolicy: Delete # volumes are automatically reclaimed when no longer in use and PVCs are deleted volumeBindingMode: WaitForFirstConsumer # Physical volumes will not be created until a pod is created that uses the PVC, required to use CSI's Topology feature parameters: csi.storage.k8s.io/fstype: ext4 type: gp3 # General Purpose SSD
DKP deploys with gp3 (general purpose SSDs) EBS volumes.
Azure CSI Driver
DKP deploys with StandardSSD_LRS for Azure Virtual Disks.
GCP CSI Driver
This driver allows volumes backed by Google Cloud Filestore instances to be dynamically created and mounted by workloads.
Driver documentation: gcp-filestore-csi-driver
Persistent volumes and dynamic provisioning: volume types
On-Premises and other storage options
In an on-premises environment, accessible storage can be used for PV and PVCs. Using the Kubernetes CSI and third party drivers, you can use your local volumes and other storage devices in your data center.