What would you like to be added:
We should expand the Flow Control configuration schema within the EndpointPickerConfig to provide a more robust and Kubernetes-native UX for defining capacity constraints.
Specifically:
- Change
maxBytes to resource.Quantity: Update the schema to allow standard k8s byte parsing (e.g., 1Gi, 500M) instead of raw int64 bytes.
- Nest Limits: Group capacity boundaries into a reusable
CapacityLimits struct embedded in the policy definitions.
- Add
maxRequests limit: Add a logical maxRequests to the CapacityLimits struct, acting as an OR shed condition alongside maxBytes.
(Note: Upgrading this schema should be done in tandem with the split default priority bands proposal tracked in #2452)
Example target schema:
flowControl:
priorityBands:
- priority: 100
limits:
maxBytes: 1Gi
maxRequests: 5000 
What would you like to be added:
We should expand the Flow Control configuration schema within the
EndpointPickerConfigto provide a more robust and Kubernetes-native UX for defining capacity constraints.Specifically:
maxBytestoresource.Quantity: Update the schema to allow standard k8s byte parsing (e.g.,1Gi,500M) instead of rawint64bytes.CapacityLimitsstruct embedded in the policy definitions.maxRequestslimit: Add a logicalmaxRequeststo theCapacityLimitsstruct, acting as anORshed condition alongsidemaxBytes.(Note: Upgrading this schema should be done in tandem with the split default priority bands proposal tracked in #2452)
Example target schema: