Skip to content

Support specifying resource requests via annotation for non-schedulable resources #6160

Closed as not planned

Description

@woehrl01

What would you like to be added:

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:

metadata:
  annotations:
    kueue.x-k8s.io/requested-resources: |
      licenses.mycompany.com/foo: "1"

Why is this needed:

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.

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature.
    on Jul 24, 2025
  2. kannon92 commented on Jul 25, 2025

    @kannon92
    Contributor

    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.

  3. woehrl01 commented on Jul 25, 2025

    @woehrl01
    ContributorAuthor

    @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

  4. k8s-triage-robot commented on Oct 23, 2025

    @k8s-triage-robot

    The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

    This bot triages un-triaged issues according to the following rules:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue as fresh with /remove-lifecycle stale
    • Close this issue with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle stale

  5. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Oct 23, 2025
  6. k8s-triage-robot commented on Nov 22, 2025

    @k8s-triage-robot

    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:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Mark this issue as fresh with /remove-lifecycle rotten
    • Close this issue with /close
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /lifecycle rotten

  7. added
    lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Nov 22, 2025
  8. k8s-triage-robot commented on Dec 22, 2025

    @k8s-triage-robot

    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:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Reopen this issue with /reopen
    • Mark this issue as fresh with /remove-lifecycle rotten
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /close not-planned

  9. k8s-ci-robot commented on Dec 22, 2025

    @k8s-ci-robot
    Contributor

    @k8s-triage-robot: Closing this issue, marking it as "Not Planned".

    Details

    In response to this:

    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:

    • After 90d of inactivity, lifecycle/stale is applied
    • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
    • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

    You can:

    • Reopen this issue with /reopen
    • Mark this issue as fresh with /remove-lifecycle rotten
    • Offer to help out with Issue Triage

    Please send feedback to sig-contributor-experience at kubernetes/community.

    /close not-planned

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions