Exception request for KEP-2400

25 views
Skip to first unread message

Ajay Sundar Karuppasamy

unread,
Jul 25, 2025, 12:08:43 PMJul 25
to releas...@kubernetes.io, kubernetes-...@googlegroups.com, kubernete...@googlegroups.com, iho...@redhat.com
Hi SIG-Node / 1.34 Release team - 

I'm submitting an exception request for KEP-2400: Node Swap Support for the upcoming Kubernetes 1.34 release.

Enhancement Details

  • Enhancement name: Kubernetes nodes support swap memory.

  • Enhancement status (alpha/beta/stable): Currently in Beta3, targeting GA in 1.34

  • SIG: Node

  • k/enhancements repo issue #: https://github.com/kubernetes/enhancements/issues/2400

  • PR #’s: 

    • #132807 this is unrelated to KEP-2400 / swap feature and seems to be a mislink.
    • #129578 is obsolete as we have decided to drop this approach. Eviction improvements are considered out of scope (context: )
    • enhancements/2400 needs description update for list of PRs.
    • Note: We believe no new code changes are pending for this KEP. Our current focus is on updating the KEP description and cleaning up obsolete or irrelevant linked issues.
  • Additional time needed (in days): 3 days (until Tuesday, this is for coordinating minor documentation/KEP cleanup, not new code development.)

  • Reason this enhancement is critical for this milestone: Enabling swap support on Kubernetes nodes is a highly anticipated feature that addresses significant customer pain points. The feature has been in Beta for a few releases and in consensus for GA. We'd like not to delay another release for a stable feature.

  • Risks from adding code late: We anticipate minimal to no risk from "adding code late" as the core code changes for basic swap enablement are largely complete and stable. The remaining tasks are primarily KEP description updates and minor cleanup, which pose no risk to the 1.34 release.

  • Risks from cutting enhancement: Cutting this enhancement from 1.34 would delay the ability for users to leverage swap, hindering critical customer use cases involving memory-intensive or bursty workloads. It would also delay the crucial feedback cycle needed for this long-awaited feature.

Thank you for your consideration.

Regards
Ajay (ajaysundark@)

Dawn Chen

unread,
Jul 25, 2025, 12:34:08 PMJul 25
to Ajay Sundar Karuppasamy, releas...@kubernetes.io, kubernetes-...@googlegroups.com, kubernete...@googlegroups.com, iho...@redhat.com
Reviewed the request, and agreed with Ajay's assessment above. 
Approve the request from the SIG Node perspective. 

Ajay, I also closed #129578 based on our decision made a while back. 

Thanks,

Dawn




--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-node" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubernetes-sig-node/CAALNpnEqn9br_kxmCgA0kyt6xrSuGzig3v_vwASO%3DwJZPtg%3DSA%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages