Uploaded image for project: 'OpenShift Container Platform (OCP) Strategy'
  1. OpenShift Container Platform (OCP) Strategy
  2. OCPSTRAT-2382

DRA: Handle extended resource requests via DRA Driver (upstream work in 4.21)

XMLWordPrintable

    • Product / Portfolio Work
    • OCPSTRAT-1692AI Workloads for OpenShift
    • 0% To Do, 100% In Progress, 0% Done
    • False
    • Hide

      None

      Show
      None
    • False
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As an OpenShift admin, I want Pods that request vendor.com/accelerator to be allocated by a DRA driver so that I can standardize on DRA (claims, policies, and lifecycle) without forcing app teams to rewrite their Pod specs.

      https://github.com/kubernetes/enhancements/issues/5004

      Why this matters (problem → outcome)

      • Today: Extended resources (e.g., GPUs) are usually exposed via device plugins; DRA is a separate path with its own objects and workflow.
      • Pain: Two parallel models to manage; hard migrations; inconsistent policy/control.
      • Outcome: Unify on DRA without breaking existing Pod specs that request vendor.com/*. Pods can keep using extended-resource fields, while a DRA driver performs the actual allocation.

              gausingh@redhat.com Gaurav Singh
              gausingh@redhat.com Gaurav Singh
              None
              Ayato Tokubi, Sai Ramesh Vanka
              Mrunal Patel Mrunal Patel
              Aruna Naik Aruna Naik
              Matthew Werner Matthew Werner
              Derrick Ornelas Derrick Ornelas
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: