dynamic resource allocation: quota = limit number of resource claims per namespace

[pohly]

As discussed in the KEP, most likely useful quotas need to be implemented by resource drivers because only they know how much resources get consumed by a specific claim.

What can be limited in Kubernetes itself is the number of ResourceClaims per namespace. For this, two new ResourceQuota resource names get added:

• resourceclaims limits the number of ResourceClaim objects in a namespace across all resource class.
• <resource-class-name>.resourceclass.node.k8s.io/resourceclaims limits the number of ResourceClaim objects for the specific resource class.

[pohly]

/sig node
/triage accepted
/priority backlog

Before we start working on this, we should know how one resource driver handles quotas and whether this is needed.

[pohly]

/priority important-soon

Let's implement this for 1.29 because it should be in place before promoting DRA to beta.

[pohly]

/assign

[k8s-triage-robot]

This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Deprioritize it with /priority important-longterm or /priority backlog
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[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

[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