-
Notifications
You must be signed in to change notification settings - Fork 159
Remove cross validation of access modes, multiple access modes can be specified that represent all the capabilities of the volume #289
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
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidz627 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 |
6d11056
to
cbb0e03
Compare
/hold |
Should we add an e2e test with multiple access modes? |
/lgtm |
@msau42 there are now unit tests with multiple access modes. K8s has e2e tests with multiple access modes that are not in the external test suites (yet, I assume) |
/hold cancel |
Do you think it is a valuable test case to add to the k8s external test suite? |
… specified that represent all the capabilities of the volume
cbb0e03
to
3d6be58
Compare
/lgtm |
/assign @msau42 @saad-ali
Needs to be cherry-picked to release-0.5.0 and new release version to be cut.
Also we should identify why none of the tests specify more than one access mode...
/kind bug