-
Notifications
You must be signed in to change notification settings - Fork 2k
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
CSI: capability block is required for volume registration #10330
Conversation
d410f87
to
245356b
Compare
245356b
to
8c28814
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.
LGTM
AccessMode: structs.CSIVolumeAccessModeMultiNodeReader, // ignored in create | ||
AttachmentMode: structs.CSIVolumeAttachmentModeFilesystem, // ignored in create | ||
AccessMode: structs.CSIVolumeAccessModeSingleNodeReader, // legacy field ignored | ||
AttachmentMode: structs.CSIVolumeAttachmentModeBlockDevice, // legacy field ignored |
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.
Should these be marked for removal in a future version?
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.
It's only deprecated for registration/creation... they're still returned on read once a claim is made.
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Add validation for
capability
blocks on volume registration (as well as creation, where it was previously documented). Update documentation and CHANGELOG for new feature and this backwards incompatibility in the volume spec.(ref #10322 for the E2E test updates for this.)