Re: 1.23 exception request for CSI migration features
Xing Yang
--Hi folks,
We would like to request an exception for the following 1.23 features that are not being promoted, however are changing the default behavior from off to on by default. These enhancements are part of the overall cloud-extraction effort.
SIG: storage
Enhancement name: AWS CSI migration
Enhancement status: remains Beta (change from off to on by default)
https://github.com/kubernetes/enhancements/issues/1487
https://github.com/kubernetes/kubernetes/pull/106098
Additional time needed (in days): 0
Reason this enhancement is critical for this milestone: This is essential for deprecating in-tree plugins and move forward for the overall CSIMigration process.
Risks from adding code late: (to k8s stability, testing, etc.): none
Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.): Delay the feature to go GA. Delay the entire migration effort.
Enhancement name: AzureDisk CSI migration
Enhancement status: remains Beta (change from off to on by default)
https://github.com/kubernetes/enhancements/issues/1490
https://github.com/kubernetes/kubernetes/pull/104670
Additional time needed (in days): 0
Reason this enhancement is critical for this milestone: This is essential for deprecating in-tree plugins and move forward for the overall CSIMigration process.
Risks from adding code late: (to k8s stability, testing, etc.): none
Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.): Delay the feature to go GA. Delay the entire migration effort.
Enhancement name: AzureFile CSI migration
Enhancement status: remains Beta (change from off to on by default)
https://github.com/kubernetes/enhancements/issues/1885
https://github.com/kubernetes/kubernetes/pull/105070
Additional time needed (in days): 0
Reason this enhancement is critical for this milestone: This is essential for deprecating in-tree plugins and move forward for the overall CSIMigration process.
Risks from adding code late: (to k8s stability, testing, etc.): none
Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.): Delay the feature to go GA. Delay the entire migration effort.
Enhancement name: GCE CSI migration
Enhancement status: remains Beta (change from off to on by default)
https://github.com/kubernetes/enhancements/issues/1488
https://github.com/kubernetes/kubernetes/pull/104722
Additional time needed (in days): 0
Reason this enhancement is critical for this milestone: This is essential for deprecating in-tree plugins and move forward for the overall CSIMigration process.
Risks from adding code late: (to k8s stability, testing, etc.): none
Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.): Delay the feature to go GA. Delay the entire migration effort.
Thanks, Michelle
You received this message because you are subscribed to the Google Groups "kubernetes-sig-storage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-st...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-storage/CAAG1FwixD1RZgH6efTM49u2_c5mctbJ4qC%3DbMvUuxZPRw_8YcQ%40mail.gmail.com.
Rey Lejano
Thank you for creating this exception request. Since we have the required approvals and the KEP has low risk we are APPROVING this request.
Please update the kep.yaml to reflect the latest milestone (1.23) and have the PR to update the kep.yaml and any open k/k PRs approved by 18:00 PST on November 16th.
If you have any questions, please feel free to reach out to us in the #sig-release Slack channel.
Thank you,
Rey Lejano
1.23 Release Team Lead
--
To unsubscribe from this group and stop receiving emails from it, send an email to release-team...@kubernetes.io.
