PoC Integration with Workload and PodGroup API#847
Conversation
|
Skipping CI for Draft Pull Request. |
k8s-ci-robot
added
do-not-merge/work-in-progress
✅ Deploy Preview for kubernetes-sigs-lws ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Edwinhr716 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
|
PR needs rebase. DetailsInstructions 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
added
needs-rebase
| k8s.io/utils v0.0.0-20251002143259-bc988d571ff4 | ||
| sigs.k8s.io/controller-runtime v0.23.3 | ||
| sigs.k8s.io/structured-merge-diff/v6 v6.4.0 | ||
| k8s.io/api v0.36.0 |
There was a problem hiding this comment.
Worth updating this outside of this POC TBH.
3 participants
What type of PR is this?
/kind feature
What this PR does / why we need it
Part of #666
This PR is a proof of concept of how the integration with Workload and PodGroup APIs would look like. Only covers LWS controller, doesn't cover DisaggregatedSet. Goal is to discover gaps with the alpha versions of PodGroup and Workload APIs when it comes to inference use cases. Doc describing implementation: https://docs.google.com/document/d/1VqfNB1u8cmrRhMe0DKycX-bfaLgDm5cgHGWdWu-94cM/edit?tab=t.0#heading=h.y6q4i0rhl51e
Which issue(s) this PR fixes
Fixes #
Special notes for your reviewer
Does this PR introduce a user-facing change?