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

Promote GetVolume and VolumeCondition to GA #517

Merged

Conversation

xing-yang
Copy link
Contributor

This PR promotes volume health monitoring related capabilities, RPCs, fields to GA.

Volume health monitoring is implemented in Kubernetes CSI External Health Monitor Controller and Kubelet.
The feature on the controller side is Alpha since Kubernetes v1.19.
The feature on the Kubelet side is Alpha since Kubernetes v1.21.
We are planning to move both to Beta in Kubernetes v1.26.
kubernetes/enhancements#3321
https://github.com/kubernetes-csi/external-health-monitor/releases

We want to move the corresponding feature in CSI spec to GA before that.

@jdef
Copy link
Member

jdef commented Jul 12, 2022

same question as on Jun 8 re: backwards compat: should alpha really be deleted, or just set to "false" ?

@xing-yang
Copy link
Contributor Author

same question as #509 (comment) re: backwards compat: should alpha really be deleted, or just set to "false" ?

@jdef regarding this question, I think it is safe to delete "alpha". After upgrading to a newer CSI spec with GetVolume and VolumeCondition without the alpha label, there won't be anything else in the system that still refers to the "alpha" API.

@saad-ali saad-ali added this to the v1.7 milestone Oct 19, 2022
Copy link
Member

@jdef jdef left a comment

Choose a reason for hiding this comment

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

LGTM

@saad-ali saad-ali merged commit 6bdbaa0 into container-storage-interface:master Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants