release-1.9 cut details for v1.9.0

[sunnylovestiramisu]

/kind feature

What this PR does / why we need it:
Put 1.9.0 release into stable-master. The sidecar update is based on this.

RC passing testgrid since 02-22 20:08 PST (visible google internal only): https://k8s-testgrid.appspot.com/provider-gcp-compute-persistent-disk-csi-driver#Kubernetes%20Master%20Driver%20Latest%20Release%20Candidate

https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-gcp-compute-persistent-disk-csi-driver-release-staging-k8s-master-integration/1628728505032249344 with newest sidecar change.

Refer to #804

None

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[sunnylovestiramisu]

/ok-to-test

[tyuchn]

/lgtm

[msau42]

In the test job linked, I don't see the driver deployed with the configuration from https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/master/deploy/kubernetes/images/prow-stable-sidecar-rc-master/image.yaml

image: k8s.gcr.io/sig-storage/csi-provisioner:v3.0.0
image: k8s.gcr.io/sig-storage/csi-attacher:v3.2.1
image: k8s.gcr.io/sig-storage/csi-resizer:v1.2.0
image: k8s.gcr.io/sig-storage/csi-snapshotter:v3.0.3
image: gcr.io/k8s-staging-cloud-provider-gcp/gcp-compute-persistent-disk-csi-driver:v1.4.0

[msau42]

It looks like the overlay used in the test is overlay_name=prow-gke-release-staging-rc-master

[msau42]

With the new link, it looks like it's testing the dev overlay, which is based off of stable-master. https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/blob/master/deploy/kubernetes/overlays/dev/kustomization.yaml#L11

[msau42]

I think you need to copy all the rc overlay changes here too.

[sunnylovestiramisu]

Done

[msau42]

I don't see the patches from #1144 here.

[sunnylovestiramisu]

https://storage.googleapis.com/kubernetes-jenkins/logs/ci-gcp-compute-persistent-disk-csi-driver-release-staging-k8s-master-integration/1628728505032249344/build-log.txt

This is not the log to look at? It says csi-attacher v4.2.0.
With the parameter:

{"name":"csi-attacher","image":"k8s.gcr.io/sig-storage/csi-attacher:v4.2.0","args":["--v=5","--csi-address=/csi/csi.sock","--http-endpoint=:22012","--leader-election","--leader-election-namespace=$(PDCSI_NAMESPACE)","--timeout=250s","--max-grpc-log-length=10000","--default-fstype=ext4"]

[sunnylovestiramisu]

Added and build bin/kustomize build deploy/kubernetes/overlays/stable-master/

- args:
        - --v=5
        - --csi-address=/csi/csi.sock
        - --http-endpoint=:22012
        - --leader-election
        - --leader-election-namespace=$(PDCSI_NAMESPACE)
        - --timeout=250s
        - --max-grpc-log-length=10000
        - --default-fstype=ext4
        env:
        - name: PDCSI_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        image: k8s.gcr.io/sig-storage/csi-attacher:v4.2.0
        livenessProbe:
          failureThreshold: 1
          httpGet:
            path: /healthz/leader-election
            port: http-endpoint
          initialDelaySeconds: 10
          periodSeconds: 20
          timeoutSeconds: 10
        name: csi-attacher
        ports:
        - containerPort: 22012
          name: http-endpoint
          protocol: TCP
        volumeMounts:
        - mountPath: /csi
          name: socket-dir

[msau42]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: msau42, sunnylovestiramisu

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [msau42]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment