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: read-repair CSI volume claims #7824

Merged
merged 2 commits into from
Apr 29, 2020
Merged

csi: read-repair CSI volume claims #7824

merged 2 commits into from
Apr 29, 2020

Conversation

tgross
Copy link
Member

@tgross tgross commented Apr 28, 2020

After 0.11.0 was shipped, in #7782 and we added some fields for CSIVolumeClaims and to the request body for CSIVolumeClaimRequest from the client. But we need to ensure these fields are present in a backwards-compatible way.

This changeset performs read-repair on CSIVolumeClaims and ensures the NodeID field is populated on claim requests when available and necessary.

(Pulled out of #7794 to reduce that changeset's scope.)

The `CSIVolumeClaim` fields were added after 0.11.1, so claims made
before that may be missing the value. Repair this when we read the
volume out of the state store.
The `NodeID` field was added after 0.11.0, so we need to ensure it's
been populated during upgrades from 0.11.0.
Copy link
Contributor

@langmartin langmartin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice, this looks good!

@tgross tgross merged commit 36e3d13 into master Apr 29, 2020
@tgross tgross deleted the csi_backwards_compat branch April 29, 2020 15:57
@github-actions
Copy link

github-actions bot commented Jan 8, 2023

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 Jan 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants