Sunny

@nixpanic NodeModifyVolume is not included in this KEP proposal. Resize API and this ModifyVolume API is two separate APIs. Are you suggesting us to consider some consecutive operations for Resizing...

This probably needs a discussion among the larger crowd. And is it possible to implement node operations later as a followup P2 and we make sure it is extensible? Basically...

Another option we discussed is: remove the annotation when the provisioner tries to access a Node that doesn't exist by detecting [errors.NewNotFound](https://github.com/kubernetes/client-go/blob/v0.26.1/listers/core/v1/node.go#L65)

Reproduced the error by the following step: 1. ``kubetest --build --up`` 2. Deploy a pd csi driver via ``[gcp-compute-persistent-disk-csi-driver/deploy/kubernetes/deploy-driver.sh](https://goto.google.com/src)`` 3. Create a storage class, create a pvc with annotation: ``volume.kubernetes.io/selected-node``,...

Manually testes with the fix https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/pull/139 1. Copy the sig-storage-lib-external-provisioner with the fix to external-attacher vendor 2. ``make container`` of a new external-attacher image 3. Upload to GCR and then...

We should cherry-pick to [external-provisioner 3.2, 3.3, 3.4](https://kubernetes-csi.github.io/docs/external-provisioner.html)

The release has been published in external-provisioner: https://github.com/kubernetes-csi/external-provisioner/releases/tag/v3.3.1 https://github.com/kubernetes-csi/external-provisioner/releases/tag/v3.2.2 https://github.com/kubernetes-csi/external-provisioner/releases/tag/v3.4.1

/close

This is an intended behavior in AP cluster, gcp_filestore_csi_driver_config will always be enabled. We only allow customers to turn it on or off for standard clusters.

Here is the wrapper script I used to generate PRs for 1.26 sidecar release: ``` #!/bin/bash die () { echo >&2 "\nERROR: $@\n" exit 1 } while read repo branches;...