Volume Provisioning Overview
The Scality CSI Driver for S3 supports two methods for creating and managing persistent volumes: Static Provisioning and Dynamic Provisioning.
Provisioning Methods Comparison
| Aspect | Static Provisioning | Dynamic Provisioning |
|---|---|---|
| Bucket Creation | Pre-created S3 bucket required | Bucket created automatically |
| Kubernetes Resources | Manual PV + PVC creation | Automatic PV creation from PVC |
| Use Case | Fixed buckets, shared storage | On-demand storage, isolated workloads |
| Management Overhead | Higher (manual PV management) | Lower (automated) |
| Resource Lifecycle | Bucket persists after PV deletion | Configurable via reclaim policy (bucket deletion only occurs if empty) |
| Multi-tenancy | Manual bucket isolation | Built-in isolation per PVC |
| Credential Management | Per-volume secrets or global | StorageClass-level configuration |
Getting Started
Quick Navigation
Static Provisioning:
- Overview & Examples - Basic concepts and step-by-step examples
- Credentials Management - Driver-level vs volume-level authentication
Dynamic Provisioning:
- Overview & Examples - StorageClass setup and workflows
- Credentials Management - Template-based and fixed authentication methods
Common Configuration:
- Mount Options Reference - Customization options for both provisioning methods
Quick Start: Static Provisioning
- Create a PersistentVolume pointing to an existing bucket
- Create a PersistentVolumeClaim that binds to the PV
- Mount the PVC in the pod
Quick Start: Dynamic Provisioning
- Create a StorageClass with S3 provisioner configuration
- Create a PersistentVolumeClaim referencing the StorageClass
- Using the CSI Driver, Kubernetes automatically creates the bucket and PV
- Mount the PVC in the pod