Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for Resource Claims and DRA #15332

Open
skonto opened this issue Jun 18, 2024 · 2 comments
Open

Support for Resource Claims and DRA #15332

skonto opened this issue Jun 18, 2024 · 2 comments
Labels
area/API API objects and controllers kind/feature Well-understood/specified features, ready for coding. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@skonto
Copy link
Contributor

skonto commented Jun 18, 2024

Describe the feature

As K8s community is actively working on moving to resource claims it would be great to add support for it at some point (adding this for future reference).
This is Alpha since 1.26, will stay so in 1.31 but it is being worked agressively see kubernetes/enhancements#3063 (comment) so soon it will move to Beta and GA it seems.

In Knative, right now trying to set a resource claim fails validation as expected:

Error from server (BadRequest): error when creating "service.yaml": admission webhook "validation.webhook.serving.knative.dev" denied the request: validation failed: must not set the field(s): spec.template.spec.containers[0].resources.claims

/area API

References

Unleashing the Power of DRA (Dynamic Resource Allocation) for Just-in-Time GPU Slicing
What Can I Get You? An Introduction to Dynamic Resource Allocation - Freddy Rolland & Adrian Chiris
Deploy vLLM server on Kubernetes using NVIDIA Kubernetes DRA driver
KCSEU 2024 - Dynamic Resource Allocation - the path towards GA - Kevin Klues Patrick Ohly
Meeting notes from K8s Serving WG
K8s issues/KEPs:
Dynamic Resource Allocation with Control Plane Controller
DRA: structured parameters

@skonto skonto added the kind/feature Well-understood/specified features, ready for coding. label Jun 18, 2024
@knative-prow knative-prow bot added the area/API API objects and controllers label Jun 18, 2024
@skonto
Copy link
Contributor Author

skonto commented Jun 18, 2024

cc @dprotaso @ReToCode

Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 17, 2024
@ReToCode ReToCode added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/API API objects and controllers kind/feature Well-understood/specified features, ready for coding. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

2 participants