The implementation of the quota-controller is currently not compatible to resources provided through the platform mesh resource-broker.
This is due to the fact, that the resource-broker owns the APIExport for the resources and therefore kcp will just look for validating web hooks in the resource-broker workspace.
This breaks the e2e responsibility approach for a service provider.
Desired outcome:
Improve on the design of the quota-controller
OR
Suggest fixes to the upstream resource-broker
OR
mark the quota-controller clearly to not be compatible to the resource-broker
Link to the resource-broker: https://github.com/platform-mesh/platform-mesh/tree/main/operators/resource-broker
The implementation of the quota-controller is currently not compatible to resources provided through the platform mesh resource-broker.
This is due to the fact, that the resource-broker owns the APIExport for the resources and therefore kcp will just look for validating web hooks in the resource-broker workspace.
This breaks the e2e responsibility approach for a service provider.
Desired outcome:
Improve on the design of the quota-controller
OR
Suggest fixes to the upstream resource-broker
OR
mark the quota-controller clearly to not be compatible to the resource-broker
Link to the resource-broker: https://github.com/platform-mesh/platform-mesh/tree/main/operators/resource-broker