WAS: Decouple PodGroup API

[helayoty]

Enhancement Description

• One-line enhancement description (can be used as a release note): Decouple PodGroup as a Runtime Object
• Kubernetes Enhancement Proposal:
• Primary contact (assignee): @helayoty @mm4tt
• Related KEPs:
  • Gang Scheduling Support in Kubernetes #4671
• Discussion Link:
  • sig-scheduling meeting Jan 22nd, 2026
  • Decoupled Workload and PodGroup APIs
  • proposded Workload v2
• PRs by stage and milestone:
  • Alpha - v1.36
    • KEP (k/enhancements) update PR(s):
      - KEP-5832: Decouple PodGroup API from Workload API #5833
      - KEP-5883: Resolve remaining wording comments #5912
    • Code (k/k) update PR(s):
      • Create Workload API v1alpha2 kubernetes#136976
    • Docs (k/website) update PR(s):
      • KEP-5832: Add docs for PodGroup API  website#54490

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

[helayoty]

/milestone v1.36
/label lead-opted-in
/triage accepted

[k8s-ci-robot]

@helayoty: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

Details

In response to this:

/sig-scheduling
/milestone v1.36
/label lead-opted-in
/triage accepted

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.

[helayoty]

/sig scheduling

[macsko]

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

[helayoty]

/assign