DRA: admin-controlled device attributes

[pohly]

Enhancement Description

• One-line enhancement description (can be used as a release note): By overriding device attributes, cluster admins can modify how devices are described with a Kubernetes API that works the same way for all DRA drivers. This mechanism is also the basis for admin-controlled device taints.
• Kubernetes Enhancement Proposal: KEP-5027 + 5055: DRA: admin-controlled device attributes + device taints #5034
• Discussion Link: DRA: mark devices as unhealthy in ResourceSlice kubernetes#128979 (comment), DRA: structured parameters: network-attached resource kubernetes#124042 (comment)
• Primary contact (assignee): @pohly
• Responsible SIGs: SIG Scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.33
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
  • 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.

[pohly]

/sig node
/sig scheduling
/wg device-management

[eero-t]

By overriding device attributes, cluster admins can prevent usage of certain devices (unhealthy, taken offline for maintenance)

How admin should run test workload(s) on device which scheduling has been disabled (e.g. for firmware upgrade), to know whether it can be enabled egain (for production workloads)?

With node taints, one would use taint tolerance for this, but I don't seem from KEP description how similar thing would be achieved for DRA devices.

[pohly]

@eero-t: let's discuss in the PR, there we have threading => https://github.com/kubernetes/enhancements/pull/5034/files#r1913015929

[kannon92]

Another one that needs an opt-in label to be tracked for enhancements.

[pohly]

/assign

[Huang-Wei]

/label lead-opted-in

[lzung]

Hello @pohly 👋, v1.33 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025.

This enhancement is targeting stage alpha for v1.33 (correct me, if otherwise)
/stage alpha

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.33.
• 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). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 6th February 2025 so that the PRR team has enough time to review your KEP.

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

• I see that there is an open PR KEP-5027 + 5055: DRA: admin-controlled device attributes + device taints #5034 containing all of the above updates. This will need to be merged prior to enhancements freeze

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!