Added patch verb for volumesnapshotcontents resource to vsphere-csi-controller-role for the compatibility with external-snapshotter 5.0

[lintongj]

What this PR does / why we need it:
Based on kubernetes-csi/external-snapshotter#526, the RABC rules for csi-snapshotter needs to be updated if vSphere CSI driver uses external-snapshotter 5.0 onward. So, we need to make this manifest update.

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

N/A

Testing done:

• Manual testing: Dynamically provision a RWO volume and provision a snapshot of the volume. Both of them works fine.

Special notes for your reviewer:

N/A

Release note:

Added patch verb for volumesnapshotcontents resource to vsphere-csi-controller-role for the compatibility with external-snapshotter 5.0

[k8s-ci-robot]

Hi @lintongj. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[lintongj]

/assign @xing-yang

[svcbot-qecnsdp]

Started vanilla Block pipeline... Build Number: 825

[lintongj]

/assign @deepakkinni

[k8s-ci-robot]

@lintongj: GitHub didn't allow me to assign the following users: deepakkinni.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign @deepakkinni

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.

[xing-yang]

So this is for the CSI snapshotter sidecar. What about rbac for snapshot-controller? Do we just directly use the ones in external-snapshotter repo?

[svcbot-qecnsdp]

Block vanilla build status: FAILURE 
Stage before exit: testbed-deployment 

[svcbot-qecnsdp]

Started vanilla Block pipeline... Build Number: 826

[svcbot-qecnsdp]

Block vanilla build status: FAILURE 
Stage before exit: testbed-deployment 

[xing-yang]

/ok-to-test

[lintongj]

So this is for the CSI snapshotter sidecar. What about rbac for snapshot-controller? Do we just directly use the ones in external-snapshotter repo?

That’s correct. This RBAC for csi snapshotter sidecar only. We always get rbac for snapshot-controller from upstream external-snapshotter repo

[xing-yang]

/approve

[deepakkinni]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deepakkinni, lintongj, xing-yang

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 [deepakkinni,xing-yang]

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