Update change log and docs for release v1.17.1 to master

[Sneha-at]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Updates the testing image to latest tag for new release and adds changelog for the new release release-1.17 branch.
Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Sneha-at / name: Sneha-at (efb4c18)

[mattcary]

/lgtm

[mattcary]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mattcary, Sneha-at

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 [mattcary]

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

[Sneha-at]

/easycla

[Sneha-at]

/easycla

[sunnylovestiramisu]

/lgtm

[mattcary]

/hold

But we do not need to change it manually anymore in test/k8s-integration/main.go? I think this comment session needs to be updated.

Oh! you're right, it does need to be kept in sync.

pdImagePlaceholder should be changed to use the registery prefix.

[Sneha-at]

@mattcary Is this the image path you were referring to? Do we also need a version?

[mattcary]

yup that's it exactly

[mattcary]

/cancel hold
/lgtm

[mattcary]

/hold cancel

[mattcary]

/hold

Actually it looks like the image tag didn't get correctly replaced. Search the k8s integration test logs for kind: Daemonset and you'll see the following

apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: csi-gce-pd-node
  namespace: gce-pd-csi-driver
spec:
  selector:
    matchLabels:
      app: gcp-compute-persistent-disk-csi-driver
  template:
    metadata:
      labels:
        app: gcp-compute-persistent-disk-csi-driver
    spec:
      containers:
      - args:
        - --v=5
        - --endpoint=unix:/csi/csi.sock
        - --run-controller-service=false
        - --enable-data-cache
        - --node-name=$(KUBE_NODE_NAME)
        env:
        - name: KUBE_NODE_NAME
          valueFrom:
            fieldRef:
              fieldPath: spec.nodeName
        image: registry.k8s.io/cloud-provider-gcp/gcp-compute-persistent-disk-csi-driver:v1.17.2
        imagePullPolicy: Always
        name: gce-pd-driver
        securityContext:
          privileged: true
        volumeMounts:
        - mountPath: /var/lib/kubelet
          mountPropagation: Bidirectional
          name: kubelet-dir
        - mountPath: /csi
          name: plugin-dir
        - mountPath: /dev
          name: device-dir
        - mountPath: /etc/udev
          name: udev-rules-etc
        - mountPath: /lib/udev
          name: udev-rules-lib
        - mountPath: /run/udev
          name: udev-socket
        - mountPath: /sys
          name: sys
        - mountPath: /lib/modules
        - ...

But the image should look something like

        image: gcr.io/k8s-infra-e2e-boskos-016/gcp-persistent-disk-csi-driver:f7544c99-5420-4f2f-bac1-88214a737d67

[Sneha-at]

/retest-required

[Sneha-at]

@mattcary I don't think there's any path update needed fro the integration test, I see the driver is built correctly

        image: gcr.io/k8s-infra-e2e-boskos-068/gcp-persistent-disk-csi-driver:0fe1554e-94d5-42a9-9fe2-8943c28cc946

Full config for controller from latest integration test run

apiVersion: apps/v1
kind: Deployment
metadata:
  name: csi-gce-pd-controller
  namespace: gce-pd-csi-driver
spec:
  replicas: 1
  selector:
    matchLabels:
      app: gcp-compute-persistent-disk-csi-driver
  template:
    metadata:
      labels:
        app: gcp-compute-persistent-disk-csi-driver
    spec:
      containers:
      - 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
        - --enable-data-cache
        - --supports-dynamic-throughput-provisioning=hyperdisk-balanced,hyperdisk-throughput,hyperdisk-ml
        - --supports-dynamic-iops-provisioning=hyperdisk-balanced,hyperdisk-extreme
        command:
        - /gce-pd-csi-driver
        env:
        - name: GOOGLE_APPLICATION_CREDENTIALS
          value: /etc/cloud-sa/cloud-sa.json
        image: gcr.io/k8s-infra-e2e-boskos-068/gcp-persistent-disk-csi-driver:0fe1554e-94d5-42a9-9fe2-8943c28cc946
        imagePullPolicy: Always
        name: gce-pd-driver
        volumeMounts:
        - mountPath: /csi
          name: socket-dir
        - mountPath: /etc/cloud-sa
          name: cloud-sa-volume
          readOnly: true

[k8s-ci-robot]

@Sneha-at: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-gcp-compute-persistent-disk-csi-driver-e2e-windows-2019	efb4c18	link	false	/test pull-gcp-compute-persistent-disk-csi-driver-e2e-windows-2019

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[mattcary]

/lgtm

[mattcary]

/hold cancel