Skip to content
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

Merged
merged 1 commit into from
Apr 8, 2021

Conversation

tgross
Copy link
Member

@tgross tgross commented Apr 8, 2021

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.)

Copy link
Contributor

@drewbailey drewbailey left a 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
Copy link
Member

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?

Copy link
Member Author

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.

@tgross tgross merged commit 45f0a3a into main Apr 8, 2021
@tgross tgross deleted the b-csi-registration-must-include-cap branch April 8, 2021 17:02
@github-actions
Copy link

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.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants