Node Declared Features (formerly Node Capabilities)

[pravk03]

Enhancement Description

• One-line enhancement description (can be used as a release note): Node Declared Features
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/5328-node-declared-features
• Discussion Link: proposal doc
• Primary contact (assignee): @pravk03
• Responsible SIGs: sig-node, sig-scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.35
  • Beta release target (x.y):
  • Stable release target (x.y):
• [x] Alpha
  • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/5347
  • [x] Code (k/k) update PR(s): https://github.com/kubernetes/kubernetes/pull/133389/
  • [x] Docs (k/website) update PR(s): https://github.com/kubernetes/website/pull/52852
• [ ] Beta
  • [ ] KEP (k/enhancements) update PR(s):
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update(s):

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

[pravk03]

/sig node /sig scheduling

[pravk03]

/cc @tallclair @dchen1107 @yujuhong

[pravk03]

edit: renaming the KEP from "Node Capability Aware Scheduling" to "Node Capabilities" as the information can also be used for API request validation (Eg: In place pod update requests).

[pravk03]

/stage alpha

[SergeyKanzhelev]

/assign @pravk03 /milestone v1.35

[rayandas]

Hi @pravk03 :wave:, v1.35 Enhancements Lead here.

It looks like this enhancement has been added to the v1.35 milestone, but doesn't yet have the lead-opted-in label. Just a gentle reminder that if you plan to work on this enhancement in v1.35, please have the SIG lead opt-in by adding the lead-opted-in label, which will ensure it gets added to the tracking board.

Thanks!

[dchen1107]

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

[pravk03]

/retitle Node Declared Features (formerly Node Capabilities)

based on the re-defined scope for the KEP

[aibarbetta]

Hello @pravk03👋, 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.

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.

With all the PRR freeze requirements in place, this enhancement is now marked as Tracked for PRR freeze! Please keep the issue description up-to-date with appropriate stages as well.

/label tracked/yes

[aibarbetta]

Hello @pravk03 👋, 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:

• [X] KEP readme using the latest template has been merged into the k/enhancements repo.
• [X] KEP status is marked as implementable for latest-milestone: v1.35. KEPs targeting stable will need to be marked as implemented after code PRs are merged.
• [X] KEP readme has up-to-date graduation criteria.
• [X] KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• [X] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

[kernel-kun]

Hello @pravk03 :wave:, v1.35 Docs Shadow here.

Does this enhancement work planned for v1.35 require any new docs or modification to existing docs?

If so, please follow the steps here to open a PR against dev-1.35 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 23th October 2025.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[chadmcrowell]

Hi @pravk03 👋 -- this is Chad (@chadmcrowell) from the 1.35 Communications Team!

For the 1.35 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement!

As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:

• This introduces some breaking change(s)
• This has significant impacts and/or implications to users
• ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉

To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Friday, the 31st of October? For more information about writing a blog, please find the blog contribution guidelines 📚

[!Tip] Some timeline to keep in mind:

• 12:00 UTC Friday, 31st October: Feature blog PR freeze
• Friday, 21st November: Feature blogs ready for review
• You can find more in the release document

[!Note] In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[kernel-kun]

Hello @pravk03 👋, this is Tushar Mittal (@kernel-kun) from v1.35 Release Docs team. We are closing in on the Placeholder PR deadline, Thursday 23rd October 2025. I'm dropping a reminder to please follow the guidelines mentioned in the quoted comment (https://github.com/kubernetes/enhancements/issues/5328#issuecomment-3409425675)

Hello @pravk03 👋, v1.35 Docs Shadow here.

Does this enhancement work planned for v1.35 require any new docs or modification to existing docs?

If so, please follow the steps here to open a PR against dev-1.35 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 23th October 2025.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[pravk03]

Hi @kernel-kun, I have created a placeholder docs PR - https://github.com/kubernetes/website/pull/52852

[chadmcrowell]

Hi @pravk03 👋, 1.35 Communications Team here again!

This is a gentle reminder for the feature blog deadline mentioned above, which is 12:00 UTC Friday, 31st October. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!

[!Tip] Some timeline to keep in mind:

• 12:00 UTC Friday, 31st October: Feature blog PR freeze
• Friday, 21st November: Feature blogs ready for review
• You can find more in the release document

[!Note] In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[aibarbetta]

Hey again @pravk03 👋 v1.35 Enhancements team here,

Just checking in as we approach code freeze and test freeze at Thursday 6th November 2025 (AoE) / Friday 7th November 2025, 12:00 UTC.

Here's where this enhancement currently stands:

• [x] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• [ ] All PRs are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

Per the issue description, these are all of the implementation (code-related) PRs for v1.35, some of which are not merged yet:

• https://github.com/kubernetes/kubernetes/pull/133389

Please let me know (and keep the issue description updated) if there are any other PRs in k/k that we should track for this KEP, so that we can maintain accurate status.

If the implementation work for this enhancement is occurring out-of-tree (i.e., outside of k/k), please link the relevant PRs in the issue description for visibility. Alternatively, if you're unable to provide specific PR links, a confirmation that all out-of-tree implementation work is complete and merged will help us finalize tracking and maintain accuracy.

The status of this enhancement is marked as At risk for code freeze.

If you anticipate missing code freeze, you can file an exception request in advance.

[aibarbetta]

With all implementation PRs merged, this is now Tracked for code freeze

/label tracked/yes

[kernel-kun]

Hello @pravk03 👋, v1.35 Docs Team here again!

Please take a look at Documenting for a release - PR Ready for Review to get your Docs PR ready for review before Tuesday 18th November 2025.

Please let us know once your PR is fully Ready for Review — meaning all documentation updates are complete and it’s awaiting reviewer feedback — so we can update our tracking.

Thank you!

[sreeram-venkitesh]

I believe the docs PR https://github.com/kubernetes/website/pull/52852 is ready for review now. I see a lot of changes and an active ongoing review.