Provisioner Selection and Configuration
What you'll learn: How to choose the right provisioner type (in-tree, CSI, or external) for your Kubernetes storage backend.
What Is a Provisioner?
A provisioner is the component that creates actual storage volumes when you request a PersistentVolumeClaim. Think of it as the translator between Kubernetes and your storage system—it speaks "Kubernetes" on one side and your cloud provider's storage API on the other.
When you define a StorageClass, the provisioner field tells Kubernetes which component handles volume creation. Choosing the right one affects reliability, features, and future compatibility.
Three Types of Provisioners
In-Tree Provisioners
These are built into Kubernetes itself (like kubernetes.io/aws-ebs or kubernetes.io/azure-disk). They're convenient because they're pre-installed, but they're being deprecated. Think of them as the old phone built into your car—they work, but can't be upgraded without replacing the whole system.
CSI (Container Storage Interface) Provisioners
These are modern, plugin-based provisioners (like ebs.csi.aws.com or disk.csi.azure.com). They run as separate pods in your cluster and follow an industry standard. They're like a smartphone mount in your car—upgradeable, flexible, and forward-compatible.
External Provisioners
These are third-party solutions for specialized storage (like NFS, Ceph, or proprietary systems). They extend Kubernetes storage beyond what cloud providers offer natively.
Which Should You Choose?
- Use CSI provisioners for all new deployments—they're the future
- Migrate from in-tree if you're using deprecated provisioners
- Use external provisioners only for non-cloud or specialized storage needs
Your StorageClass configuration drives which provisioner handles requests, impacting features like snapshots, cloning, and encryption support.
Key Takeaway: Always prefer CSI provisioners for cloud storage—they're actively maintained, feature-rich, and the industry standard going forward.