Groups keyboard shortcuts have been updated
Dismiss
See shortcuts
Release exception for KEP-2400
155 views
Skip to first unread message
Peter Hunt
Oct 10, 2024, 8:30:16 PM10/10/24
to kubernetes-...@googlegroups.com, releas...@kubernetes.io, kubernetes-sig-node
Hey all, I'd like to make an exception for 1.32
Enhancement name: KEP 2400 - node memory swap support
Enhancement status (alpha/beta/stable): stable or a retargeted beta
SIG: sig-node
k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/2400
PR #’s: Implementation PR: https://github.com/kubernetes/enhancements/pull/4701
Additional time needed (in days): 4 days (EOD EST Wednesday)
Reason this enhancement is critical for this milestone: Users are eager for the stabilization of swap
Risks from adding code late: (to k8s stability, testing, etc.) The goal of the extension is to ensure swap is as stable as possible. It potentially will involve retargeting beta to include more things, the SIG needs more time to discuss pros and cons.of each approach
Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.) A delay in the stablization of swap. If there are additional action items for beta, we should figure them out and move towards them ASAP. If the feature is ready for GA, then we should work towards that to stabilize the API users have been using
Enhancement status (alpha/beta/stable): stable or a retargeted beta
SIG: sig-node
k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/2400
PR #’s: Implementation PR: https://github.com/kubernetes/enhancements/pull/4701
Additional time needed (in days): 4 days (EOD EST Wednesday)
Reason this enhancement is critical for this milestone: Users are eager for the stabilization of swap
Risks from adding code late: (to k8s stability, testing, etc.) The goal of the extension is to ensure swap is as stable as possible. It potentially will involve retargeting beta to include more things, the SIG needs more time to discuss pros and cons.of each approach
Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.) A delay in the stablization of swap. If there are additional action items for beta, we should figure them out and move towards them ASAP. If the feature is ready for GA, then we should work towards that to stabilize the API users have been using
Thank you for your time and consideration
Reply all
Reply to author
Forward
0 new messages