Can we get Persistent Volume with only PVC without PV in k8s?
System Design practice on Codemia
Work through 120+ system design problems with detailed solutions, from rate limiters to multi-region storage.
Understanding Persistent Volume Claims in Kubernetes
Kubernetes is widely known for its robust system of managing containerized applications, but the platform also includes complex storage solutions that sometimes appear confusing at a first glance. One of the most common questions among Kubernetes users is whether it is possible to obtain a Persistent Volume (PV) using only a Persistent Volume Claim (PVC), without explicitly creating or defining a PV. Let's explore the technical details behind this and see how Kubernetes simplifies storage provisioning with features like dynamic provisioning.
The PVC/PV Relationship
In Kubernetes, storage solutions are abstracted by two main concepts:
- Persistent Volume (PV): A piece of storage in the cluster with a lifecycle independent of any individual pod that uses the PV. It is defined by an admin using a variety of storage backends.
- Persistent Volume Claim (PVC): A request for storage by a user. This request allows users to use abstract storage without needing to know the specific details of the backends or the PVs.
Traditionally, an administrator would first create a PV and then a user would claim storage by creating a PVC that binds to a pre-existing PV.
Dynamic Provisioning
Kubernetes simplifies storage management through a feature called Dynamic Provisioning. This provision method allows users to create PVCs that automatically provision a PV, abstracting the administration layer and simplifying operations.
How Dynamic Provisioning Works
- StorageClass Definition: Administrators define a `StorageClass` which specifies the provisioner (e.g., AWS EBS, GCE PD, NFS), parameters, and reclaim policies.
- ReadWriteOnce
- ReadWriteOnce
- Reclaim Policy: Defined in `StorageClass`, it determines what happens to a PV after its released. Normally set to `Retain`, `Recycle`, or `Delete`.
- StorageClass Parameters: The specific parameters for cloud providers or provisioners, such as volume type or zone, must be configured correctly to use dynamic provisioning effectively.
- Access Modes: Defines how a PV can be mounted by pods (ReadWriteOnce, ReadWriteMany).
Related reading
- Can we have same kind of multiple containers in a Pod in Kubernetes?
- Can we see transfer progress with kubectl cp?
- Can we use data as a yaml file instead of Json file in Config map
- Can We use Multiple AWS ACM Certificates at Nginx-Ingress-Contoller OR Multiple ACM certificate at Ingress object level?
- Can we restore to same dynamodb table from backup
- Can we set Strong Consistent Read on DynamoDB after creation
- Can you auto destroy a kubernetes pod deployment?
- Can you define Kubernetes Services / Pods using YAML in Terraform?
System Design Fundamentals
Build a strong foundation in designing scalable, reliable distributed systems.
View the courseTrack what you have practised
A free account saves your progress, solutions and study plan across every problem on Codemia.
System Design practice on Codemia
Work through 120+ system design problems with detailed solutions, from rate limiters to multi-region storage.