Kubernetes Storage: A
Deep Look
IT practitioners have long sought a solution for the ever-changing challenges of
storage. The latest innovation? Containers! These systems not only make it easier
than ever to store data, but also allow you greater flexibility and portability across
environments - something that's impossible with traditional approaches.
Kubernetes Storage is a service that lets you dynamically provision, attach, and
mount storage volumes on Kubernetes clusters. You can use the service to store
pod data as well as build stateful applications on top of your deployed pods.
The following types of storage are currently available:
Persistent Volume (PV) – Similar to AWS EBS or GCE PD, this provides
persistent block storage volumes that survive the deletion of pods that consume
them. It utilizes many drivers to enable it's functionality such as NFS, Ceph,
Flocker etc., depending upon your underlying infrastructure layer (e.g. AWS).
These drivers abstract complexities such as network setup/configuration and
physical disk management from developers/operators.
Dynamic Volume Provisioning – Provides dynamically provisioned volumes. This
volume type is backed by a block storage pool configured by the administrator,
which can be any cloud or on-premise storage providers who provide Amazon
Elastic Block Store (EBS) volume compatible API.
The PersistentVolume object represents persistent storage resources in
Kubernetes storage. You can use this resource to dynamically provision and
manage Persistent Volumes for your applications.
A persistent volume claim is used to request a volume with specific parameters
from an available persistent volume source that satisfies the requestor's
namespace configuration and access mode requirements.
A dynamic volume provisioner provides dynamically provisioned volumes. These
are mounted into pods created by kubelets when they see a volume being claimed
by a pod.
It does not have many use cases as it just makes the process of using different
types of storage easier for developers/operators who want to consume that
specific type of storage, but at the same time their usage is limited as they cannot
provide the required features such as QoS and access modes.
A Kubernetes Storage can be backed by various types of storage providers,
including cloud-based storage solutions as well as on-premise installations. In
order to allow provisioning from these different technologies, different types of
dynamic volume provisioners exist.

Kubernetes Storage a Deep Look

  • 1.
  • 2.
    IT practitioners havelong sought a solution for the ever-changing challenges of storage. The latest innovation? Containers! These systems not only make it easier than ever to store data, but also allow you greater flexibility and portability across environments - something that's impossible with traditional approaches.
  • 3.
    Kubernetes Storage isa service that lets you dynamically provision, attach, and mount storage volumes on Kubernetes clusters. You can use the service to store pod data as well as build stateful applications on top of your deployed pods.
  • 4.
    The following typesof storage are currently available: Persistent Volume (PV) – Similar to AWS EBS or GCE PD, this provides persistent block storage volumes that survive the deletion of pods that consume them. It utilizes many drivers to enable it's functionality such as NFS, Ceph, Flocker etc., depending upon your underlying infrastructure layer (e.g. AWS). These drivers abstract complexities such as network setup/configuration and physical disk management from developers/operators.
  • 5.
    Dynamic Volume Provisioning– Provides dynamically provisioned volumes. This volume type is backed by a block storage pool configured by the administrator, which can be any cloud or on-premise storage providers who provide Amazon Elastic Block Store (EBS) volume compatible API.
  • 6.
    The PersistentVolume objectrepresents persistent storage resources in Kubernetes storage. You can use this resource to dynamically provision and manage Persistent Volumes for your applications.
  • 7.
    A persistent volumeclaim is used to request a volume with specific parameters from an available persistent volume source that satisfies the requestor's namespace configuration and access mode requirements.
  • 8.
    A dynamic volumeprovisioner provides dynamically provisioned volumes. These are mounted into pods created by kubelets when they see a volume being claimed by a pod.
  • 9.
    It does nothave many use cases as it just makes the process of using different types of storage easier for developers/operators who want to consume that specific type of storage, but at the same time their usage is limited as they cannot provide the required features such as QoS and access modes.
  • 10.
    A Kubernetes Storagecan be backed by various types of storage providers, including cloud-based storage solutions as well as on-premise installations. In order to allow provisioning from these different technologies, different types of dynamic volume provisioners exist.