StorageClass Parameters
What you'll learn: How to use provisioner-specific parameters in StorageClass resources to control storage characteristics like volume type, performance, and availability.
The Core Idea
In the previous lesson, you learned what a StorageClass is—a blueprint for dynamically provisioning storage. Now we'll explore the parameters field, which lets you customize exactly what kind of storage gets created.
Think of StorageClass parameters like ordering a custom pizza. The provisioner (pizza maker) is specified, but parameters let you choose: thin crust or thick? Extra cheese? Garlic butter? Similarly, storage parameters let you specify: SSD or HDD? High IOPS? Multi-zone replication?
How Parameters Work
Each storage provisioner (AWS EBS, Azure Disk, GCE PD, Ceph, etc.) accepts different parameters. These are key-value pairs in the StorageClass definition:
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: fast-ssd
provisioner: kubernetes.io/aws-ebs
parameters:
type: gp3
iopsPerGB: "50"
encrypted: "true"
kmsKeyId: arn:aws:kms:us-east-1:123456789:key/abc-123
In this AWS EBS example:
- type: specifies the volume type (gp3 = general purpose SSD)
- iopsPerGB: controls performance (input/output operations per second)
- encrypted: enables encryption at rest
- kmsKeyId: specifies which encryption key to use
Different provisioners have completely different parameters. Azure might use storageaccounttype, GCE might use replication-type. Always consult your provisioner's documentation.
Why This Matters
Without parameters, you get default storage—which might be slow, unencrypted, or unsuitable for production databases. Parameters give you fine-grained control over cost, performance, and durability without manually creating volumes.
Key Takeaway: StorageClass parameters are provisioner-specific settings that define the characteristics of dynamically created volumes, letting you control performance, encryption, replication, and other storage features through declarative configuration.