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
deprecate csi migration for ceph rbd #118303
deprecate csi migration for ceph rbd #118303
Conversation
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/sig storage |
cde771b
to
8a80d35
Compare
8a80d35
to
4e6d929
Compare
What are we deprecating? The changelog isn't clear. Are we asking people not to migrate (deprecation means “please stop doing”)? Maybe: Deprecated support for CSI migration of Ceph RBD volumes.
Users who were relying on Kubernetes' ability to migrate to an out-of-tree storage driver should complete
that migration before the support for it is removed. |
@sftim thanks for your comment. It's updated now. |
/lgtm from rbd pov |
/lgtm |
LGTM label has been added. Git tree hash: fa6065465c39cb8c0591971617f0652bbfbf088c
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: carlory, xing-yang 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 |
Thanks @xing-yang 👍 |
@xing-yang true. @carlory can you please add ACTION required as I have done @ #118552 |
@xing-yang updated. |
What type of PR is this?
/kind deprecation
What this PR does / why we need it:
Based on https://groups.google.com/g/kubernetes-sig-storage/c/h5751_B5LQM, the consensus was to start the deprecation in v1.28.
This commit start the deprecation process of RDB plugin from in-tree drivers.
kubernetes/enhancements#2923 (comment)
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: