Adjusting a ResourcePoolClaim?

[keeprocking]

Hi,

Is there a way to adjust a ResourcePoolClaim? Or, at least, delete it and create a new one with an updated .spec.claim?

Use case

I'm building a multi-tenant cluster where each tenant has a dedicated share of resources. Tenants can split their available quota across namespaces as they see fit. I thought the ResourcePool / ResourcePoolClaim combination would be a perfect fit:

• ResourcePool defines the tenant's total available quota and is configured by cluster admins. Each tenant has its own ResourcePool.
• ResourcePoolClaim is created in each namespace and configured by tenants depending on the workload.

The issue

Tenants often need to redistribute their quota across namespaces, but this currently seems impossible because ResourcePoolClaim is immutable. It's mentioned in the docs that a claim can be released, but that doesn't seem to work:

1. A bound claim cannot be deleted:

   Error from server (Forbidden): admission webhook "resourcepoolclaims.projectcapsule.dev" denied the request: cannot delete the pool while claim is bound to a resourcepool foo-virtual
   

2. When I apply the projectcapsule.dev/release: "true" annotation, it appears to be immediately removed by the controller. The claim remains bound and still cannot be deleted.

The only workaround I've found so far is deleting the entire namespace, which is overkill for a simple quota adjustment. Ideally, there should be a way to adjust a claim as long as the total sum of claims for a given tenant stays within the ResourcePool limits.

Any advice would be much appreciated.

Thanks.

[oliverbaehler]

This will be fixed with the next release.

[keeprocking]

Thank you.

When is the next release planned?