Kubernetes Persistent Volume Provisioner from pre-created snapshots.
- You create PersistentVolumeClaim with empty Storage class (for disable Dynamic Provisioning)
- pv-provisioner detect PVC and track tag
app
value - pv-provisioner search most actual snapshot with label
app
value equalapp
tag of k8s PVC - pv-provisioner create new Disk/Volume
- pv-provisioner create new PersistentVolume with required params
- PVC use created PV
Please follow charts/pv-provisioner/README.md
- "gcp" - Google Cloud Platform
- if you're using Kubernetes Serviceaccount with
Workload Identity
please set appropriate annotations to the service account invalues.yaml
file.
- if you're using Kubernetes Serviceaccount with
- GCP_PROJECT - GCP project ID
- GCP_ZONE - GCP Disks availability zone
- GCP_SNAPSHOT_LABEL - tag name for find Snapshot
- GCP_DISK_TYPE - Disk type resource describing which disk type to use to create the disk. For example:
pd-ssd