DRA KEP 5018: Admin Access #3230

Description

Overview

Admin Access enables the creation of privileged mode ResourceClaim and ResourceClaimTemplates. These claims can bind to already allocated devices and are intended for admin tasks like health reporting / monitoring.

The ResourceClaim schema has been extended to include an adminAccess field per request:

apiVersion: resource.k8s.io/v1beta1
kind: ResourceClaim
metadata:
  name: admin-resource-claim
  namespace: admin-namespace
spec:
  devices:
    requests:
      - deviceClassName: admin-resource-class
        adminAccess: true

Additionally, the claim's namespace must be allowlisted for the creation of admin-access claims through the use of a label:

metadata:
  labels:
    resource.kubernetes.io/admin-access: "true"

Karpenter Integration

Admin access allows a claim to bind to a device that is already allocated, even if that device does not explicitly enable multiple allocations. Karpenter's DRA allocator should expand the set of eligible placement options to include allocated devices for admin access claims.

This should be a straightforward integration.

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• Comments asking for updates generate extra noise for issue followers and do not help maintainers prioritize issues. If you think the issue is higher priority than it is labelled, please instead add your user story.
• If you are interested in working on this issue or have submitted a pull request, please assign yourself