Volumes (Kubernetes)
Jump to navigation
Jump to search
↑ https://kubernetes.io/docs/concepts/storage/volumes/
↑ https://kubernetes.io/docs/concepts/storage/volumes/#types-of-volumes
↑ https://kubernetes.io/docs/concepts/storage/#fc
↑ https://kubernetes.io/docs/concepts/storage/volumes/#flexVolume
↑ https://kubernetes.io/docs/concepts/storage/persistent-volumes/#expanding-persistent-volumes-claims
Kubernetes Volumes allows to store data independent of Container restarts. Volumes in Kubernetes are different that Docker Volumes.[1]
Kubernetes supports different type of volumes [2]:
- Cloud providers: awsElasticBlockStore, azureDisk, azureFile
- Storage technologies: fc (fibre channel)[3], iscsi
- Networked filesystems: cephfs, nfs, glusterfs
- Others:
- cinder, configMap, CSI, downwardAPI
- emptyDir: the data in the emptyDir is deleted forever when Pod is removed from a node.
- flexVolume[4], can be expanded [5]
- flocker, gcePersistentDisk, hostPath, local, persistentVolumeClaim, projected, portworxVolume, quobyte, rbd, scaleIO, secret, storageos, vsphereVolume
- Support for raw block storage in CSI (v1.18, March 2020)
- Deprecated: gitRepo
Persistent volumes subsystem provides an API for users and administrators that abstracts details of how storage is provided from how it is consumed.
Related terms
- CKA v1.18: Understand persistent volumes and know how to create them
- CKA v1.15: Understand PersistentVolumeClaims for storage
Activities
See also
- Persistent Volumes
- Certified Kubernetes Administrator: Understand PersistentVolumeClaims for storage
- Pods
Advertising: