Kubernetes Storage Concepts: Difference between revisions
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
Provisioner. | Provisioner. | ||
Old plugins used to be. Newer plugins are based on the [[#CSI|Container Storage Interface (CSI)]]. | |||
=<span id='Container_Storage_Interface'></span><span id='CSI'></span>Container Storage Interface (CSI)= | =<span id='Container_Storage_Interface'></span><span id='CSI'></span>Container Storage Interface (CSI)= |
Revision as of 00:59, 10 December 2019
Internal
Overview
Kubernetes has a mature and feature-rich subsystem called the persistent volume subsystem. Regardless of where it comes from, storage is exposed to the Kubernetes cluster in the form of a volume.
Storage Providers
Storage is exposed to a Kubernetes cluster by storage providers.
The Kubernetes persistent volume subsystem supports, among others:
- iSCSI
- SMB
- Enterprise storage arrays from vendors like EMC and NetApp
- NFS
- object storage blobs
- Amazon Elastic Block Store block devices
- Azure File resources
- GCE Persistent Disks
Each storage provider has its own plugin that handles the details of exposing the storage to the Kubernetes cluster.
Storage Plugin
Provisioner.
Old plugins used to be. Newer plugins are based on the Container Storage Interface (CSI).
Container Storage Interface (CSI)
API Resources
PersistentVolume (PV)
PersistentVolumeClaim (PVC)
StorageClass (SC)
Volume
Secrets may be exposed as files in dedicated volumes mounted in the pod.
Volume Type
- hostPath
- configMap
Dynamic Volume Provisioning
Dynamic volume provisioner https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/