What would you like to be added?

Kubernetes clusters on top of GCE should use community maintained binaries, the CSI Proxy binary used in kubernetes/kubernetes comes from a release pipeline owned by the GKE team.

Why is this needed?

The current process to use a new CSI Proxy binary is as follows:

• A CSI Proxy owner makes a release cut e.g. https://github.com/kubernetes-csi/csi-proxy/releases/tag/v1.2.1
• In GKE, an automated pipeline detects a new tag and builds the binary and makes it available in a staging bucket.
• In GKE, a GKE dev promotes the binary to the prod bucket gke-release
• In upstream kubernetes/kubernetes, we use the binary promoted to the gke-release bucket e.g. Bump CSI Proxy to v1.2.1-gke.2 #131146

Ideally, upstream kubernetes should rely on binaries created in upstream build pipelines. The process could look like the following:

• A CSI Proxy owner makes a release cut e.g. https://github.com/kubernetes-csi/csi-proxy/releases/tag/v1.2.1.
• A post tag Github Action runs automatically and builds the binary and attaches the artifacts to the release.
• In upstream kubernetes/kubernetes, we use the binary available as attached resources in the new tag.

Mirror bug in CSI Proxy: kubernetes-csi/csi-proxy#83

/cc @sunnylovestiramisu @tonyzhc