Use sig-storage-lib-external-provisioner v7.0.1

[wongma7]

What type of PR is this?
/kind bug

What this PR does / why we need it: the newer lib contains the fix for #576
kubernetes-sigs/sig-storage-lib-external-provisioner#104

from release note https://github.com/kubernetes-sigs/sig-storage-lib-external-provisioner/releases/tag/v7.0.0:

• Set provision-by anno to the storage class provisioner Set provision-by anno to the storage class provisioner kubernetes-sigs/sig-storage-lib-external-provisioner#104 *
  • Previous behavior: the pv.kubernetes.io/provisioned-by PV annotation was always set to the Controller's primary provisionerName
  • New behavior: if additionalProvisionerNames is passed to the Controller then the pv.kubernetes.io/provisioned-by PV annotation is set to the provisionerName or additionalProvisionerNames equal to the PV's StorageClass.
    • For example, if you have a Controller with provisionerName: ebs.csi.aws.com and additionalProvisionerNames: [kubernetes.io/aws-ebs] then PVs created for StorageClass with provisioner: ebs.csi.aws.com will have annotation pv.kubernetes.io/provisioned-by: ebs.csi.aws.com and PVs created for StorageClass with provisioner: kubernetes.io/aws-ebs will have annotation pv.kubernetes.io/provisioned-by: kubernetes.io/aws-ebs

In addition, the newer lib lets us remove the serverVersion check at startup.

Which issue(s) this PR fixes:
Fixes #645

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Newly provisioned CSI Migration enabled PV will have "provisioned-by" annotation set to in-tree provisioner name instead of the CSI provisioner

[k8s-ci-robot]

Hi @wongma7. Thanks for your PR.

I'm waiting for a kubernetes-csi member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[msau42]

/ok-to-test
/assign @Jiawei0227

[Jiawei0227]

/lgtm
/approve

[msau42]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jiawei0227, msau42, wongma7

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