WARNING: Manual deployment of this driver to your GKE cluster is not recommended. Instead users should use GKE to automatically deploy and manage the GCE PD CSI Driver (see GKE Docs).
DISCLAIMER: Manual deployment of the driver to your cluster is not officially supported by Google.
The Google Compute Engine Persistent Disk CSI Driver is a CSI Specification compliant driver used by Container Orchestrators to manage the lifecycle of Google Compute Engine Persistent Disks.
Status: GA
Latest stable image: gcr.io/gke-release/gcp-compute-persistent-disk-csi-driver:v1.2.1-gke.0
| Driver Version | Kubernetes Version | Test Status |
|---|---|---|
| HEAD Latest | HEAD | |
| 0.7.x stable | HEAD | |
| HEAD Latest | HEAD (Migration ON) | |
| HEAD stable-master | HEAD (Migration ON) |
This plugin is compatible with CSI versions v1.2.0, v1.1.0, and v1.0.0
The following table captures the compatibility matrix of the core persistent disk driver binary
gke.gcr.io/gcp-compute-persistent-disk-csi-driver
| GCE PD CSI Driver\Kubernetes Version | 1.15 | 1.16 | 1.17+ |
|---|---|---|---|
| v0.2.x (alpha) | no | no | no |
| v0.3.x (beta) | yes | yes | yes |
| v0.4.x (beta) | yes | yes | yes |
| v0.5.x (beta) | yes | yes | yes |
| v0.6.x (beta) | yes | yes | yes |
| v0.7.x (beta) | yes | yes | yes |
| v1.0.x (ga) | yes | yes | yes |
| dev | yes | yes | yes |
The manifest bundle which captures all the driver components (driver pod which includes the containers csi-provisioner, csi-resizer, csi-snapshotter, gce-pd-driver, csi-driver-registrar; csi driver object, rbacs, pod security policies etc) can be picked up from the master branch overlays directory. We structure the overlays directory, per minor version of kubernetes because not all driver components can be used with all kubernetes versions. For example volume snapshots are supported 1.17+ kubernetes versions thus stable-1-16 driver manifests does not contain the snapshotter sidecar.
Example:
stable-1-19 overlays bundle can be used to deploy all the components of the driver on kubernetes 1.19.
stable-master overlays bundle can be used to deploy all the components of the driver on kubernetes master.
For more details about per k8s minor version overlays, please check this doc
See Github Issues
| Parameter | Values | Default | Description |
|---|---|---|---|
| type | pd-ssd OR pd-standard |
pd-standard |
Type allows you to choose between standard Persistent Disks or Solid State Drive Persistent Disks |
| replication-type | none OR regional-pd |
none |
Replication type allows you to choose between Zonal Persistent Disks or Regional Persistent Disks |
| disk-encryption-kms-key | Fully qualified resource identifier for the key to use to encrypt new disks. | Empty string. | Encrypt disk using Customer Managed Encryption Key (CMEK). See GKE Docs for details. |
| labels | key1=value1,key2=value2 |
Labels allow you to assign custom GCE Disk labels. |
This driver supports only one topology key:
topology.gke.io/zone
that represents availability by zone (e.g. us-central1-c, etc.).
GCE PD driver starts to support CSI Windows with [CSI Proxy] (https://github.com/kubernetes-csi/csi-proxy). It requires csi-proxy.exe to be installed on every Windows node. Please see more details in CSI Windows page (docs/kubernetes/user-guides/windows.md)
| Feature | Stage | Min Kubernetes Master Version | Min Kubernetes Nodes Version | Min Driver Version | Deployment Overlay |
|---|---|---|---|---|---|
| Snapshots | Alpha | 1.13 | Any | v0.3.0 | Alpha |
| Snapshots | Beta | 1.17 | Any | v1.0.0 | stable-1-17, stable-1-18, stable-1-19, stable-master |
| Resize (Expand) | Alpha | 1.14 | 1.14 | v0.6.0 | Alpha |
| Resize (Expand) | Beta | 1.16 | 1.16 | v0.7.0 | stable-1-16, stable-1-17, stable-1-18, stable-1-19, stable-master |
| Windows* | Beta | 1.18 | 1.18 | v1.1.0 | stable-1-18, stable-1-19, stable-master |
* For Windows, it is recommended to use this driver with CSI proxy v0.2.2+. The master version of driver requires disk v1beta2 group, which is only available in CSI proxy v0.2.2+
See Github Issues
As part of the deployment process, the driver is deployed in a newly created namespace by default. The namespace will be deleted as part of the cleanup process.
Controller-level and node-level deployments will both have priorityClassName set, and the corresponding priority value is close to the maximum possible for user-created PriorityClasses.