You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support specifying resource requests via annotation for non-schedulable resources #6160
Support for specifying resource requests via pod annotations, so that Kueue can manage resources like licenses that are not tied to node-level capacity. For example:
Some resources, like commercial licenses, are globally limited and I want to manage by Kueue but not advertise by any node. Using resources.requests for such resources results in pods being unschedulable because the scheduler expects the resource to be present in node capacity. Allowing resource requests via annotations would let Kueue enforce global quotas without interfering with the scheduler.
I don't think annotations would be right here as Kueue computes resources based on the requests.
I do have some questions for you though:
Its also not clear to me if your licenses are at container level or pod level. If I have a pod with 5 containers that call your application, does that require 5 licenses?
Another possiblity could be to limit pods. You could maybe consider a combination of resource flavors with ClusterQueue on quota limiting pods.
@kannon92 thanks, I already stumbled over the transformer, but the docs aren't exactly clear where in the process it sits. Would I add the requests as "license" on the requests and remove it via the transformer?
If I look it from the kep you sent it seems that it's more the other way around, to merge requests, so that you don't have to overcomplicate the flavours.
To your questions, I now see the possible mismatch. But in our case it would map to the pod, not container level
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.
Activity
kannon92 commentedon Jul 25, 2025
Thinking about this, maybe the resourceTransformations feature would be useful for you.
https://github.com/kubernetes-sigs/kueue/tree/main/keps/2937-resource-transformer#story-2
I don't think annotations would be right here as Kueue computes resources based on the requests.
I do have some questions for you though:
Its also not clear to me if your licenses are at container level or pod level. If I have a pod with 5 containers that call your application, does that require 5 licenses?
Another possiblity could be to limit pods. You could maybe consider a combination of resource flavors with ClusterQueue on quota limiting pods.
woehrl01 commentedon Jul 25, 2025
@kannon92 thanks, I already stumbled over the transformer, but the docs aren't exactly clear where in the process it sits. Would I add the requests as "license" on the requests and remove it via the transformer?
If I look it from the kep you sent it seems that it's more the other way around, to merge requests, so that you don't have to overcomplicate the flavours.
To your questions, I now see the possible mismatch. But in our case it would map to the pod, not container level
k8s-triage-robot commentedon Oct 23, 2025
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
k8s-triage-robot commentedon Nov 22, 2025
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
k8s-triage-robot commentedon Dec 22, 2025
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/reopen/remove-lifecycle rottenPlease send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
k8s-ci-robot commentedon Dec 22, 2025
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
Details
In response to this:
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.