-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Map PV access modes to CSI access modes based on driver capability #308
Map PV access modes to CSI access modes based on driver capability #308
Conversation
fd63e4c
to
ab0e373
Compare
ab0e373
to
69fb259
Compare
dc26ef0
to
e4c4d38
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have couple of nits, but the PR goes the right direction.
vendor/github.com/kubernetes-csi/csi-lib-utils/accessmodes/access_modes.go
Outdated
Show resolved
Hide resolved
887792f
to
f4499f0
Compare
032fd34
to
282fa01
Compare
/hold Rebased on #317 which is blocked on release of v1.22. |
282fa01
to
5c66da5
Compare
/hold cancel |
5c66da5
to
00dde3e
Compare
00dde3e
to
bbc9af1
Compare
@jsafrane PTAL, this is ready for review |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chrishenzie, jsafrane 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:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
See KEP#2485 for more details.
This PR introduces mappings between Kubernetes PV access modes and CSI access modes. If the CSI driver supports the
SINGLE_NODE_MULTI_WRITER
controller capability, map ReadWriteOnce toSINGLE_NODE_MULTI_WRITER
and ReadWriteOncePod toSINGLE_NODE_SINGLE_WRITER
. If the CSI driver does not support this controller capability, map ReadWriteOnce toSINGLE_NODE_WRITER
(current behavior preserved for backwards compatibility).Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
The CSI spec change PR#476 is here and just requires merging. Until then, I have a placeholder commit using my forked version of the CSI spec.
Similarly for K8s, the API change and feature addition PR#102028 is here and still is in the early stages of review. Until then, I have a placeholder commit using my forked version of the K8s API.
Does this PR introduce a user-facing change?:
/assign @msau42
/assign @jingxu97