Kubernetes Storage Concepts

Internal

• Kubernetes Concepts

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 volumes
• SMB
• Enterprise storage arrays from vendors like EMC and NetApp
• NFS volumes
• object storage blobs
• Amazon Elastic Block Store block devices
• Azure File resources (AzureDisk).
• GCE Persistent Disks

Each storage provider has its own plugin that handles the details of exposing the storage to the Kubernetes cluster.

Storage Plugins

The terms "storage plugin" and "provisioner" are used interchangeably.

Old storage plugins used to be implemented as part of the main Kubernetes code tree (in-tree), which raised a series of problems, such as that all had to be open-source and their release cycle was tied to the Kubernetes release cycle.

Newer plugins are based on the Container Storage Interface (CSI).

Container Storage Interface (CSI)

Container Storage Interface (CSI) is an open standard that provides a clean interface for storage plugins and abstracts the internal Kubernetes storage details.

API Resources

The persistent volume subsystem consists of the following three primitives that allow applications to consume storage:

PersistentVolume (PV)

A single external storage volume can only be used by a single persistent volume.

PersistentVolumeClaim (PVC)

A persistent volume claim is similar to a ticket that authorizes a pod to use a certain persistent volume.

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/

Organizatorium

• GlusterFS Kubernetes