Node Readiness Gates

[ajaysundark]

Enhancement Description

• One-line enhancement description (can be used as a release note): Node Readiness Gates
• Kubernetes Enhancement Proposal:
• Discussion Link: https://github.com/kubernetes/kubernetes/issues/131208 Proposal: doc here
• Primary contact (assignee): @ajaysundark
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.35
  • Beta release target (x.y):
  • Stable release target (x.y):
• [ ] Alpha
  • [ ] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/5416
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[ajaysundark]

/sig node /cc @aojea @danwinship

[ffromani]

/sig scheduling /cc

[sanposhiho]

/cc @kubernetes/sig-scheduling-approvers

[sanposhiho]

/cc @macsko @dom4ha

didn't realize the approver team doesn't include you guys rn

[atiratree]

/sig apps as this feature pertains to DaemonSets

[xing-yang]

/sig storage

[haircommander]

/milestone v1.35 /label lead-opted-in

[kannon92]

/assign @ajaysundark

[rayandas]

Hello @ajaysundark 👋, v1.35 Enhancements team here.

This is a reminder of the upcoming PRR freeze on Thursday 9th October 2025 (AoE) / Friday 10th October 2025, 12:00 UTC.

This enhancement is targeting stage Alpha for v1.35 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [x] PR open or merged with the KEP's PRR questionnaire filled out.
• [x] PR open or merged with kep.yaml updated with the stage, latest-milestone, and milestone struct filled out.
• [x] PR open or merged with a PRR approval file with the PRR approver listed for the stage the KEP is targeting.

For this KEP, we would just need to update the following:

• Fill the PRR questionnaire
• Add a PRR approver

Note that the PRs are not required to be approved or merged by the PRR freeze deadline. Having the PRR questionnaire filled out by the deadline will help ensure that the PRR team has enough time to review your KEP before enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC. For more information on the PRR process, see here.

The status of this enhancement is marked as At risk for PRR freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing PRR freeze, you can file an exception request in advance. Thank you!

[rayandas]

This PR (https://github.com/kubernetes/enhancements/pull/5416) checks all the requirements for PRR freeze, hence this KEP is now Tracked for PRR freeze. Thanks! /label tracked/yes

[rayandas]

Hello @ajaysundark 👋, v1.35 Enhancements team here.

Just checking in as we approach enhancements freeze on Thursday 16th October 2025 (AoE) / Friday 17th October 2025, 12:00 UTC.

This enhancement is targeting stage Alpha for v1.35 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [ ] KEP readme using the latest template has been merged into the k/enhancements repo.
• [ ] KEP status is marked as implementable for latest-milestone: v1.35.
• [ ] KEP readme has up-to-date graduation criteria.
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

For this KEP, we would just need to update the following:

• Please get approvals on this PR https://github.com/kubernetes/enhancements/pull/5416

The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!

[rayandas]

Hello @ajaysundark 👋, v1.35 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in v1.35, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

/label tracked/no /milestone clear

[pacoxu]

link to the new repo: https://github.com/kubernetes-sigs/node-readiness-controller

[rayandas]

Hi @ajaysundark 👋 v1.35 Enhancements Team here.

We are nearing the close of the v1.35 release. As part of the end of release cleanup, we are removing the lead-opted-in label to prepare for the next cycle.

If you would like this enhancement to be considered for the next release, please have the SIG lead opt in again by re adding the label and setting the appropriate milestone for the new release. This ensures the enhancement appears on the tracking board.

Thanks!

/remove-label lead-opted-in