9.5. Dynamic provisioning
Table of Contents
Understanding Dynamic Provisioning
Dynamic provisioning in OpenShift automates the creation of persistent storage when a pod (through a PersistentVolumeClaim) asks for it. Instead of pre-creating PersistentVolumes (PVs), the cluster allocates and binds storage on demand using a StorageClass and a provisioner (often a CSI driver).
You should already be familiar with PVs, PVCs, and StorageClasses from previous chapters; here we focus on what is unique about dynamic provisioning: how it works, how it is configured in OpenShift, and what to watch out for.
How Dynamic Provisioning Works
At a high level, the flow is:
- A user (or application) creates a
PersistentVolumeClaimthat: - Requests a certain size (
resources.requests.storage) - Optionally selects a
StorageClass(viastorageClassName) - The control plane sees the PVC is unbound and has a
storageClassName. - The associated storage provisioner (defined by the
StorageClass) is called. - The provisioner:
- Talks to the underlying storage system (CSI driver, cloud API, etc.)
- Creates a new volume that satisfies the claim
- Creates a
PersistentVolumeobject referencing that backend volume - Kubernetes binds the new PV to the PVC.
- Pods referencing the PVC can now mount and use the dynamically created volume.
If no appropriate StorageClass and provisioner can satisfy the request, the PVC will stay in Pending state.
Role of StorageClasses in Dynamic Provisioning
Dynamic provisioning is driven entirely by StorageClass definitions. Each StorageClass describes:
- The provisioner (
provisioner/csidriver name) - Parameters specific to the storage backend
- Reclaim policy (
reclaimPolicy) - Volume binding behavior (
volumeBindingMode) - Whether it is the default
StorageClassfor the cluster
A minimal example:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: fast-ssd
provisioner: kubernetes.io/no-provisioner # for illustration; real classes use a CSI driver
parameters:
type: ssd
reclaimPolicy: Delete
allowVolumeExpansion: true
volumeBindingMode: WaitForFirstConsumerIn OpenShift, storage vendors or the platform itself usually install and configure production-ready StorageClasses via Operators (e.g., for OpenShift Data Foundation, AWS EBS, Azure Disk, etc.).
Default StorageClass
If exactly one StorageClass carries the annotation:
metadata:
annotations:
storageclass.kubernetes.io/is-default-class: "true"
then PVCs without an explicit storageClassName will use that class automatically. This is how most dynamic provisioning happens in typical OpenShift clusters: application developers only create PVCs; they do not manage PVs or StorageClasses directly.
Creating PVCs for Dynamic Provisioning
A PVC that leverages dynamic provisioning looks like this:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: my-data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 20Gi
storageClassName: fast-ssdKey points specific to dynamic provisioning:
storageClassNamemust match an existingStorageClasswith a valid provisioner.- If
storageClassNameis omitted: - The cluster may use the default
StorageClassif one exists. - If no default exists, the PVC will stay
Pending. accessModesmust be supported by the underlying class (e.g., some only supportReadWriteOnce).
Once the PVC is created:
- A PV is automatically created and bound.
- The PV’s
spec.storageClassNamematches the PVC’sstorageClassName. - The PV’s
spec.claimRefpoints to the PVC.
Provisioners in OpenShift
OpenShift uses the standard Kubernetes dynamic provisioning framework, with provisioners usually implemented as CSI (Container Storage Interface) drivers. Typical categories:
- Cloud provider drivers (when OpenShift runs on a public cloud):
- AWS EBS, Azure Disk/File, GCP Persistent Disk, etc.
- On-premise and enterprise storage drivers:
- OpenShift Data Foundation (ODF) / Ceph-based
- NetApp, Dell, Pure Storage, etc.
- Local or special-purpose drivers:
- Local storage (for special cases, not generic shared storage)
- File-based drivers (NFS, SMB) via appropriate CSI implementations
In many setups, these are managed by Operators that:
- Deploy the CSI driver
- Create or suggest recommended
StorageClasses(e.g.,ocs-storagecluster-ceph-rbd,gp2-csion AWS) - Handle updates and health checks
As a user of dynamic provisioning, you usually only need to know:
- What StorageClasses are available.
- Which one you should use for your workload (e.g., “standard”, “fast”, “encrypted”, “object storage gateway”, etc.).
Volume Binding Modes
Dynamic provisioning includes when and where volumes actually get created. This is controlled by the volumeBindingMode on a StorageClass:
Immediate(default Kubernetes behavior):- Volume is provisioned as soon as the PVC is created.
- Suitable in environments where topology (zones, nodes) is not a concern.
WaitForFirstConsumer:- Volume provisioning is delayed until a pod using the PVC is scheduled.
- The scheduler knows which node or zone the pod will run in, and can request the volume in a matching topology zone.
- Common for cloud and distributed storage to avoid cross-zone attachment issues.
Example:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: zonal
provisioner: my.csi.example.com
volumeBindingMode: WaitForFirstConsumer
In OpenShift, cloud-integrated and ODF classes often use WaitForFirstConsumer to ensure efficient placement and avoid scheduling conflicts.
Reclaim Policy and Dynamic Provisioning
The reclaimPolicy on a StorageClass (or PV) determines what happens to dynamically provisioned volumes after the PVC is deleted:
Delete:- Underlying storage object is deleted along with the PV.
- Common for ephemeral or per-app volumes.
Retain:- PV and underlying storage are preserved.
- Manual cleanup or re-attachment is required.
- Used when data must be preserved past application lifecycle.
With dynamic provisioning, Delete is typical for many workloads, but for critical or compliance-sensitive data, storage administrators may create special StorageClasses with Retain.
Allowing Volume Expansion
Dynamic provisioning also intersects with volume expansion. A StorageClass can enable online or offline resizing through:
allowVolumeExpansion: trueIf supported by the driver and storage backend, you can then increase the size of a PVC:
- Edit the PVC
spec.resources.requests.storageto a larger value. - The CSI driver expands the underlying volume.
- The filesystem is resized (often automatically if supported).
Dynamic provisioning plus expansion makes storage management largely self-service:
- Developers request storage.
- Later, they can grow it without creating a new volume and migrating data (within driver limits).
Dynamic Provisioning in Multi-Tenant OpenShift Clusters
In OpenShift’s multi-tenant model, dynamic provisioning is particularly valuable because:
- Project (namespace) owners can request storage without cluster-admin access.
- Administrators expose appropriate
StorageClassesand quota policies. - Per-project resource quotas can limit the total storage requested.
Dynamic provisioning considerations in such environments:
- Quotas: PVC creation will fail (or stay
Pending) if it violatesrequests.storageor object-count quotas. - Access controls: Some clusters may restrict which
StorageClassesa given project can use (for example, via admission controllers). - Cost and performance: Different
StorageClassescan represent different cost tiers or performance levels; teams may be guided or restricted to particular classes.
Observing and Troubleshooting Dynamic Provisioning
When dynamic provisioning does not behave as expected, focus on:
- PVC status:
kubectl get pvc/oc get pvcPendingindicates no PV can be bound or created.- Events on the PVC:
- Check with
oc describe pvc <name>. - Look for messages like “no persistent volumes available”, “failed to provision volume”, “storageclass not found”.
- StorageClass and provisioner health:
- Ensure
StorageClass.storageClassNamematches exactly. - Check CSI driver pods / Operator status in
openshift-storageor vendor-specific namespaces. - Topology / access mode issues:
- For
WaitForFirstConsumer, a PVC may stay unbound until a pod is actually created. - Some drivers do not support requested access modes or volume modes (
FilesystemvsBlock).
Typical failure patterns:
- Missing or mis-typed
storageClassName→ PVCPending, no events about PV creation. - Provisioner not installed or failing → events indicating failure to provision volume.
- Quota exceeded → events referencing resource quota violations.
Best Practices for Using Dynamic Provisioning in OpenShift
- Prefer dynamic provisioning over static PV management for most workloads.
- Use clearly named
StorageClassesthat indicate intent:standard,fast,archive,encrypted, etc. - Align
volumeBindingModewith your environment: - Use
WaitForFirstConsumerin zoned or multi-availability setups. - Choose
reclaimPolicybased on data sensitivity: Deletefor scratch / rebuildable data.Retainfor important or compliance-regulated data.- Enable
allowVolumeExpansionwhere your backend supports online or offline resizing. - Document which
StorageClassesare recommended for which application profiles (databases, logs, object storage gateways, etc.). - Regularly review dynamically provisioned PV usage to manage capacity planning and costs.
Dynamic provisioning is the core mechanism that turns OpenShift storage into a self-service platform: developers and workloads request persistent storage declaratively, and the cluster, via its provisioners and StorageClasses, allocates and manages the backing volumes automatically.
Views: 0
Where to Move
Move chapter:
- ☰ 1. Course Overview
- ☰ 1.1. What is OpenShift
- ☰ 1.2. Why OpenShift is used in modern IT and cloud environments
- ☰ 1.3. OpenShift vs Kubernetes
- ☰ 1.4. Typical OpenShift use cases
- ☰ 1.5. Structure and goals of the course
-
- ☰ 2. Containers and Cloud-Native Fundamentals
- ☰ 2.1. What is a container
- ☰ 2.2. Containers vs virtual machines
- ☰ 2.3. Introduction to Docker and container images
- ☰ 2.4. Container registries
- ☰ 2.5. Basics of cloud-native applications
-
- ☰ 3. Kubernetes Fundamentals
- ☰ 3.1. What is Kubernetes
- ☰ 3.2. Kubernetes architecture
- ☰ 3.3. Control plane components
- ☰ 3.4. Worker node components
- ☰ 3.5. Kubernetes objects and resources
- ☰ 3.6. Declarative configuration model
-
- ☰ 4. OpenShift Architecture
- ☰ 4.1. Overview of OpenShift architecture
- ☰ 4.2. Control plane in OpenShift
- ☰ 4.3. Nodes and machine roles
- ☰ 4.4. OpenShift Operators
- ☰ 4.5. OpenShift networking model
- ☰ 4.6. OpenShift storage model
-
- ☰ 5. OpenShift Installation and Deployment Models
- ☰ 5.1. OpenShift deployment options
- ☰ 5.2. Installer-Provisioned Infrastructure
- ☰ 5.3. User-Provisioned Infrastructure
- ☰ 5.4. Managed OpenShift services
- ☰ 5.5. Single-node OpenShift
- ☰ 5.6. Cluster lifecycle management
-
- ☰ 6. Accessing and Using OpenShift
- ☰ 6.1. OpenShift web console
- ☰ 6.2. OpenShift CLI (oc)
- ☰ 6.3. Authentication and authorization
- ☰ 6.4. Projects and namespaces
- ☰ 6.5. Resource quotas and limits
-
- ☰ 7. Building and Deploying Applications
- ☰ 7.1. Application deployment concepts
- ☰ 7.2. Source-to-Image (S2I)
- ☰ 7.3. Container-based deployments
- ☰ 7.4. DeploymentConfigs and Deployments
- ☰ 7.5. Rolling updates and rollbacks
-
- ☰ 8. Networking in OpenShift
- ☰ 8.1. Services and service discovery
- ☰ 8.2. Routes and ingress
- ☰ 8.3. Network policies
- ☰ 8.4. Load balancing
- ☰ 8.5. External access to applications
-
- ☰ 9. Storage in OpenShift
- ☰ 9.1. Persistent storage concepts
- ☰ 9.2. Persistent Volumes
- ☰ 9.3. Persistent Volume Claims
- ☰ 9.4. StorageClasses
- ☰ 9.5. Dynamic provisioning
- ☰ 9.6. Stateful applications
-
- ☰ 10. Configuration and Secrets Management
- ☰ 10.1. ConfigMaps
- ☰ 10.2. Secrets
- ☰ 10.3. Environment variables
- ☰ 10.4. Managing sensitive data
- ☰ 10.5. Best practices for configuration
-
- ☰ 11. Scaling and High Availability
- ☰ 11.1. Horizontal pod autoscaling
- ☰ 11.2. Vertical scaling
- ☰ 11.3. Self-healing and pod restarts
- ☰ 11.4. High availability concepts
- ☰ 11.5. Multi-zone and multi-region clusters
-
- ☰ 12. Monitoring, Logging, and Observability
- ☰ 12.1. Built-in monitoring stack
- ☰ 12.2. Metrics and alerts
- ☰ 12.3. Logging architecture
- ☰ 12.4. Distributed tracing
- ☰ 12.5. Troubleshooting applications
-
- ☰ 13. Security in OpenShift
- ☰ 13.1. Security model overview
- ☰ 13.2. Role-Based Access Control
- ☰ 13.3. Security Context Constraints
- ☰ 13.4. Image security and scanning
- ☰ 13.5. Network security
- ☰ 13.6. Compliance and auditing
-
- ☰ 14. CI/CD and DevOps with OpenShift
- ☰ 14.1. DevOps concepts
- ☰ 14.2. CI/CD pipelines overview
- ☰ 14.3. OpenShift Pipelines (Tekton)
- ☰ 14.4. GitOps with Argo CD
- ☰ 14.5. Integrating OpenShift with external CI tools
-
- ☰ 15. Operators and Platform Services
- ☰ 15.1. What are Operators
- ☰ 15.2. Operator Lifecycle Manager
- ☰ 15.3. Installing and managing Operators
- ☰ 15.4. Common platform Operators
- ☰ 15.5. Custom Operators
-
- ☰ 16. Upgrades, Maintenance, and Operations
- ☰ 16.1. OpenShift upgrade process
- ☰ 16.2. Backup and restore
- ☰ 16.3. Node maintenance
- ☰ 16.4. Cluster troubleshooting
- ☰ 16.5. Capacity planning
-
- ☰ 17. OpenShift on HPC and Specialized Workloads
- ☰ 17.1. Running batch workloads on OpenShift
- ☰ 17.2. OpenShift and GPUs
- ☰ 17.3. MPI and parallel workloads in containers
- ☰ 17.4. Hybrid HPC and cloud workflows
-
- ☰ 18. OpenShift in Practice
- ☰ 18.1. Typical OpenShift workflows
- ☰ 18.2. Development to production lifecycle
- ☰ 18.3. Case studies from industry
- ☰ 18.4. Common pitfalls and best practices
-
- ☰ 19. Future Directions and Ecosystem
- ☰ 19.1. Kubernetes ecosystem overview
- ☰ 19.2. OpenShift roadmap
- ☰ 19.3. Serverless and event-driven workloads
- ☰ 19.4. AI and data platforms on OpenShift
-
- ☰ 20. Final Project and Hands-On Exercises
- ☰ 20.1. Deploying a containerized application
- ☰ 20.2. Implementing CI/CD with OpenShift
- ☰ 20.3. Securing and scaling an application
- ☰ 20.4. Monitoring and troubleshooting report
-
Comments
Please login to add a comment.
Don't have an account? Register now!