skip to content
Astro Cactus

Kubernetes Storage: Understanding Volumes, PVs, and PVCs

/ 2 min read

kubernetes , k8s , storage , persistence , devops , cloud-native , containers , series:kubernetes:3

Kubernetes Storage Concepts

Storage management in Kubernetes is designed to handle both ephemeral and persistent data. Understanding these concepts is crucial for maintaining stateful applications.

Volumes

Basic Volume Types

Kubernetes supports various volume types:

  1. emptyDir

    • Temporary storage
    • Lifecycle tied to Pod
    • Useful for sharing data between containers

  2. hostPath

    • Mounts from host node
    • Persistent across Pod restarts
    • Limited to single node usage

  3. configMap/secret

    • Configuration data
    • Mounted as volumes
    • Dynamic updates possible

Cloud Provider Volumes

Popular cloud storage options:

  • AWS EBS
  • Azure Disk
  • Google Persistent Disk
  • OpenStack Cinder

Persistent Volumes (PV)

PVs are cluster resources that provide storage:

  • Lifecycle independent of Pods
  • Can be provisioned statically or dynamically
  • Support various access modes
  • Can be retained or deleted after use

Example PV:

apiVersion: v1
kind: PersistentVolume
metadata:
  name: example-pv
spec:
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Retain
  storageClassName: standard
  hostPath:
    path: /mnt/data

Persistent Volume Claims (PVC)

PVCs are requests for storage by users:

  • Abstract storage details
  • Can specify size and access modes
  • Bound to specific PV
  • Used by Pods

Example PVC:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: example-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi
  storageClassName: standard

Storage Classes

StorageClasses enable dynamic provisioning:

  • Define storage profiles
  • Automatic PV creation
  • Support various provisioners
  • Custom parameters

Example StorageClass:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: fast
provisioner: kubernetes.io/aws-ebs
parameters:
  type: gp2
reclaimPolicy: Delete
allowVolumeExpansion: true

Volume Snapshots

Features for data protection:

  • Point-in-time copies
  • Backup and restore
  • Migration support
  • Version control

Best Practices

1. Capacity Planning

  • Right-size volumes
  • Monitor usage
  • Plan for growth
  • Consider costs

2. Performance

  • Choose appropriate storage class
  • Monitor I/O metrics
  • Consider workload requirements
  • Use local storage when needed

3. Data Protection

  • Regular backups
  • Use snapshots
  • Implement disaster recovery
  • Test restore procedures

4. Security

  • Encrypt data at rest
  • Use appropriate access modes
  • Implement RBAC
  • Follow security policies

Common Use Cases

  1. Databases

    • Persistent storage
    • High performance
    • Data protection
    • Backup support

  2. Shared Storage

    • Multiple readers
    • Cross-pod access
    • File sharing
    • Content management

  3. Cache Storage

    • Fast access
    • Temporary data
    • Session management
    • Build artifacts

Troubleshooting

Common issues and solutions:

  1. Volume Mount Issues

    • Check permissions
    • Verify paths
    • Review mount options
    • Check node capacity

  2. PV Binding Problems

    • Verify storage class
    • Check capacity
    • Review access modes
    • Check provisioner status

Conclusion

Understanding Kubernetes storage is essential for running stateful applications. This guide covered the fundamentals, but storage management continues to evolve with new features and best practices.

Series Navigation