Skip to main content

Documentation Index

Fetch the complete documentation index at: https://notes.kodekloud.com/llms.txt

Use this file to discover all available pages before exploring further.

Welcome to this comprehensive guide on persistent volumes in Kubernetes. In previous lessons, we introduced the concept of volumes. Now, we focus on persistent volumes and explore how they centralize storage management for a scalable, production-ready environment.

​
Traditional Volume Configuration

Previously, storage details were embedded directly into the pod specification file. For example: 
volumes:
- name: data-volume
  awsElasticBlockStore:
    volumeID: <volume-id>
    fsType: ext4
Although this approach works for simple deployments, it becomes cumbersome in large, multi-user environments. Each pod requires its own storage configuration, making global updates difficult and error-prone.

​
Centralized Storage with Persistent Volumes

Persistent volumes solve these challenges by separating storage configuration from the pod definitions. Cluster administrators create a pool of storage resources, and users claim storage via Persistent Volume Claims (PVCs). This model simplifies management and reduces redundancy across the environment.
The image illustrates the relationship between Persistent Volume Claims (PVC) and Persistent Volumes (PVs) in a Kubernetes environment.
In summary:
  • Administrators manage storage centrally.
  • Users claim storage as needed without repetitive configuration.
  • Global changes and updates become easier to implement.

​
Creating a Persistent Volume

In this section, we create a persistent volume using a YAML template. Begin by updating the API version, setting the kind to PersistentVolume, and naming the volume (e.g., PV-01). Within the spec section, include:
  • Access Modes: Determines how a volume can be mounted (e.g., ReadOnlyMany, ReadWriteOnce, ReadWriteMany).
  • Capacity: Specifies the allocated storage size (1Gi in this example).
  • Volume Type: Here, we use a host path to utilize local node storage.
While using a hostPath is useful for demonstration purposes, it is not recommended for production environments. Always opt for a supported production-ready storage solution.
Below is an example of a persistent volume definition: 
apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv-voll
spec:
  accessModes:
    - ReadWriteOnce
  capacity:
    storage: 1Gi
  hostPath:
    path: /tmp/data

​
Deploying the Persistent Volume

To create the persistent volume, run the following command in your terminal: 
kubectl create -f pv-definition.yaml
After deployment, verify that the persistent volume has been successfully created by executing: 
kubectl get persistentvolume
This command lists all available persistent volumes, including the one you just created.

​
Conclusion

Persistent volumes in Kubernetes enable centralized storage management that streamlines deployments and simplifies ongoing maintenance. By externalizing storage configuration via PVCs, you ensure efficient resource utilization and easier scalability. For further information, visit the Kubernetes Documentation. Happy deploying!

Watch Video