Update documentation for ControllerModifyVolume and controller default

Author: travisyx

deploy/kubernetes/base/controller/controller.yaml

@@ -141,6 +141,8 @@ spec:
           args:
             - "--v=5"
             - "--endpoint=unix:/csi/csi.sock"
+            - "--supports-dynamic-iops-provisioning=hyperdisk-balanced,hyperdisk-extreme"
+            - "--supports-dynamic-throughput-provisioning=hyperdisk-balanced,hyperdisk-throughput,hyperdisk-ml"
           env:
             - name: GOOGLE_APPLICATION_CREDENTIALS
               value: "/etc/cloud-sa/cloud-sa.json"

deploy/kubernetes/images/prow-stable-sidecar-rc-master/image.yaml

@@ -7,39 +7,39 @@ metadata:
   name: imagetag-csi-provisioner-prow-rc
 imageTag:
   name: registry.k8s.io/sig-storage/csi-provisioner
-  newTag: "v3.4.0"
+  newTag: "v5.1.0"
 ---
 apiVersion: builtin
 kind: ImageTagTransformer
 metadata:
   name: imagetag-csi-attacher-prow-rc
 imageTag:
   name: registry.k8s.io/sig-storage/csi-attacher
-  newTag: "v4.2.0"
+  newTag: "v4.4.3"
 ---
 apiVersion: builtin
 kind: ImageTagTransformer
 metadata:
   name: imagetag-csi-resize-prow-rc
 imageTag:
   name: registry.k8s.io/sig-storage/csi-resizer
-  newTag: "v1.7.0"
+  newTag: "v1.11.1"
 ---
 apiVersion: builtin
 kind: ImageTagTransformer
 metadata:
   name: imagetag-csi-snapshotter-prow-head
 imageTag:
   name: registry.k8s.io/sig-storage/csi-snapshotter
-  newTag: "v6.1.0"
+  newTag: "v6.3.3"
 ---
 apiVersion: builtin
 kind: ImageTagTransformer
 metadata:
   name: imagetag-csi-node-registrar-prow-rc
 imageTag:
   name: registry.k8s.io/sig-storage/csi-node-driver-registrar
-  newTag: "v2.7.0"
+  newTag: "v2.9.3"
 ---
 apiVersion: builtin
 kind: ImageTagTransformer

docs/kubernetes/user-guides/controller-modify-volume.md

@@ -0,0 +1,41 @@
+# ControllerModifyVolume User Guide
+
+>**Attention:** VolumeAttributesClass is a Kubernetes Beta feature since v1.31, but was initially introduced as an alpha feature in v1.29. See [this blog post](https://kubernetes.io/docs/concepts/storage/volume-attributes-classes/) for more information on VolumeAttributesClasses and how to enable the feature gate.
+
+### ControllerModifyVolume Example
+
+This example provisions a hyperdisk-balanced and then updates its IOPS and throughput.
+
+1. Create the VolumeAttributesClasses (VACs), PVC, Storage Classes, and Pod
+``` 
+$ kubectl apply -f ./examples/kubernetes/demo-vol-create.yaml
+```
+
+This creates the VACs silver and gold, with the VAC for silver being the initial metadata for the PV and gold representing the update. This file also create a storage class test-sc. Note that the IOPS/throughput takes priority from the VACs if they are different. Then, a PVC is created, specifying the storage class for the PV being test-sc and the VAC being silver. Finally, a pod is created with the volume being created from the PVC we defined.
+
+2. Verify the PV is properly created
+```
+$ kubectl get pvc
+NAME        STATUS    VOLUME      CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS    AGE
+test-pvc     Bound     {pv-name}   64Gi       RWO            test-sc        silver                   {some-time}
+```
+
+3. Update the IOPS/throughput for the created PV
+```
+$ kubectl apply -f ./examples/kubernetes/demo-vol-update.yaml
+```
+
+4. Verify the PV VAC is properly updated
+```
+$ kubectl get pvc
+NAME        STATUS    VOLUME      CAPACITY   ACCESS MODES   STORAGECLASS   VOLUMEATTRIBUTESCLASS    AGE
+test-pvc     Bound     {pv-name}   64Gi       RWO            test-sc        gold                   {some-time}
+```
+
+After verifying the VAC is updated from the PV, we can check that the IOPS and throughput are properly updated.
+
+```
+$ gcloud compute disks describe {pv-name} --zone={pv-zone}
+```
+
+Ensure that the provisionedIops and provisionedThroughput fields match those from the gold VAC. Note that it will take a few minutes for the value updates to be reflected 

examples/kubernetes/demo-vol-create.yaml

@@ -0,0 +1,59 @@
+apiVersion: storage.k8s.io/v1
+kind: StorageClass
+metadata:
+  name: test-sc
+provisioner: pd.csi.storage.gke.io
+parameters:
+  type: "hyperdisk-balanced"
+  provisioned-iops-on-create: "3000"
+  provisioned-throughput-on-create: "150Mi"
+volumeBindingMode: WaitForFirstConsumer
+---
+apiVersion: storage.k8s.io/v1beta1
+kind: VolumeAttributesClass
+metadata:
+  name: silver
+driverName: pd.csi.storage.gke.io
+parameters:
+  iops: "3000"
+  throughput: "150"
+---
+apiVersion: storage.k8s.io/v1beta1
+kind: VolumeAttributesClass
+metadata:
+  name: gold
+driverName: pd.csi.storage.gke.io
+parameters:
+  iops: "3013"
+  throughput: "151"
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: test-pvc
+spec:
+  storageClassName: test-sc
+  volumeAttributesClassName: silver
+  accessModes:
+    - ReadWriteOnce
+  resources:
+    requests:
+      storage: 64Gi
+---
+apiVersion: v1
+kind: Pod
+metadata:
+  name: nginx
+spec:
+  volumes:
+  - name: vol
+    persistentVolumeClaim:
+      claimName: test-pvc
+  containers:
+  - name: nginx
+    image: nginx:1.14.2
+    ports:
+    - containerPort: 80
+    volumeMounts:
+    - mountPath: "/vol"
+      name: vol

examples/kubernetes/demo-vol-update.yaml

@@ -0,0 +1,12 @@
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: test-pvc
+spec:
+  storageClassName: test-sc
+  volumeAttributesClassName: gold
+  accessModes:
+    - ReadWriteOnce
+  resources:
+    requests:
+      storage: 64Gi

examples/kubernetes/demo-vol-update.yml

@@ -118,7 +118,7 @@ else
   base_cmd="${base_cmd} --snapshotclass-files=pd-volumesnapshotclass.yaml"
 fi
 
-if [ "$test_volumeattributesclass" = true]; then
+if [ "$test_volumeattributesclass" = true ]; then
   base_cmd="${base_cmd} --volumeattributesclass-files=hdb-volumeattributesclass.yaml --storageclass-for-vac-file=sc-hdb.yaml --kube-runtime-config=api/all=true"
 fi