KEP-5945: DRA Optional Node Preparation

[jiefeng-xu]

What type of PR is this?

/kind feature

What this PR does / why we need it:

Adds a new KEP draft for DRA optional node preparation:

• KEP: keps/sig-node/5945-dra-optional-node-preparation/
• Title: KEP-5945: DRA Optional Node Preparation

The proposal introduces explicit opt-out semantics for DRA allocations where
node-local lifecycle is not required, while preserving strict behavior by
default.

Key points in the draft:

• New feature gate: DRANodePreparation
• New optional fields:
  • DeviceRequestAllocationResult.requiresNodePreparation
  • DeviceClassSpec.requiresNodePreparation
• Default-safe semantics (nil means required)
• Kubelet skips prepare/unprepare only for explicitly opted-out allocations

Which issue(s) this PR is related to:

Part of #5945
Related context:

• DRA: kubelet: Allow option to skip plugin calls and/or NodeUnprepareResources specifically if noop kubernetes#137122

Special notes for your reviewer:

This is an initial KEP draft in provisional state. Feedback requested for:

• API field placement and semantics
• Kubelet behavior for mixed required/no-op allocations
• Graduation criteria and PRR assumptions

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

- [KEP]: /keps/sig-node/5945-dra-optional-node-preparation/README.md

[k8s-ci-robot]

Welcome @jiefeng-xu!

It looks like this is your first PR to kubernetes/enhancements 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/enhancements has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @jiefeng-xu. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jiefeng-xu
Once this PR has been reviewed and has the lgtm label, please assign dchen1107 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• keps/sig-node/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment