feat: ReadWriteOncePod support

[andyzhangx]

What type of PR is this?
/kind feature

What this PR does / why we need it:

• chore: upgrade to csi spec v1.5.0
• feat: ReadWriteOncePod support which is alpha feature in k8s 1.22

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

feat: ReadWriteOncePod support

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andyzhangx

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

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

[chrishenzie]

In order to provide full support for this feature, you will also need to advertise the SINGLE_NODE_MULTI_WRITER node and controller capabilities here.

These capabilities are required because CSI clients like the external-provisioner, attacher, and kubelet use them to determine which mapping of Kubernetes access modes to CSI access modes to use. Please see this part of the feature blog for more details, and here for more context on the motivations.

As a stretch goal we will eventually want to implement the NodePublishVolume behavior however this behavior is not currently asserted in the CSI sanity test suite. Once it's added we should update the test suite again and add support.

Let me know if you have any questions, thanks again for taking a look at this!

[andyzhangx]

In order to provide full support for this feature, you will also need to advertise the SINGLE_NODE_MULTI_WRITER node and controller capabilities here.

These capabilities are required because CSI clients like the external-provisioner, attacher, and kubelet use them to determine which mapping of Kubernetes access modes to CSI access modes to use. Please see this part of the feature blog for more details, and here for more context on the motivations.

As a stretch goal we will eventually want to implement the NodePublishVolume behavior however this behavior is not currently asserted in the CSI sanity test suite. Once it's added we should update the test suite again and add support.

Let me know if you have any questions, thanks again for taking a look at this!

@chrishenzie thanks for the review, I have added `SINGLE_NODE_MULTI_WRITER cap for both node and controller. Agree that we should add sanity test for this feature in the future.

[chrishenzie]

@andyzhangx Just checking, were you able to smoke test this driver in a cluster with the feature enabled and the right sidecars? I may be able to test myself but I'll need some time before I can get to it

[andyzhangx]

disable GetCapabilities sanity test temporally, need to upgrade csi-test later:

Summarizing 2 Failures:
[Fail] Controller Service [Controller Server] ControllerGetCapabilities [It] should return appropriate capabilities 
/home/prow/go/src/github.com/kubernetes-csi/csi-test/pkg/sanity/controller.go:151
[Fail] Node Service NodeGetCapabilities [It] should return appropriate capabilities 
/home/prow/go/src/github.com/kubernetes-csi/csi-test/pkg/sanity/node.go:345
Ran 28 of 78 Specs in 87.955 seconds
FAIL! -- 26 Passed | 2 Failed | 1 Pending | 49 Skipped

[andyzhangx]

@andyzhangx Just checking, were you able to smoke test this driver in a cluster with the feature enabled and the right sidecars? I may be able to test myself but I'll need some time before I can get to it

@chrishenzie not yet, while I could try this feature later, this PR just adds the ReadWriteOncePod cap first.

[andyzhangx]

BTW, github action unit test failure is expected since https://coveralls.io/ is down for one day.

[chrishenzie]

@andyzhangx The feature should work with these changes (implementing NodePublishVolume behavior is more for adhering to the CSI spec than it is a requirement for ReadWriteOncePod to work)

[andyzhangx]

let's merge first