Feature
core/concurrency-limit
Caps how many requests a gateway carries at once — the control that keeps a burst of callers from becoming a queue at the upstream. scope names what one cap counts: gateway, every request the gateway forwards, counted together; or model, each target the gateway sends requests to, counted apart. A target is each upstream entry the gateway routes to, so where one model name has several entries each entry is counted apart. The count is per running proxy, so where several replicas run each of them admits max_in_flight: size it against one replica, not against the whole. Every input is the operator's, so the operator attaches it in the Release, on the gateway's entry under that component's features, and sets max_in_flight in infra, with scope where the default, gateway, is not the count wanted. It attaches to a component in the request path that declares it can keep such a cap (dataplane.aggrega.ai/concurrency-cap, whichever value), and each realization refuses the scope its gateway does not count, naming the cap the gateway keeps. On core/gateway/nginx scope gateway is realized and a request past the cap is answered 503; scope model is refused, because NGINX keeps one total. On core/gateway/envoy-gateway scope model is realized, one cap for each wired model, and a request past it is answered 503; scope gateway is refused, because Envoy Gateway keeps a cap for each backend and none on their total. On core/gateway/litellm scope model is realized, one cap for each entry of its model map, and a request past it is answered 429 unless a fallback chain sends it on; scope gateway is refused, because the proxy keeps no total that holds.
Procedencia
- Digest del contenido
- sha256:8f20e59cffb4e898dccdc2abb9e12c3c2cd3c9409b8350257d8aca7c121ec73e
- Publicado
- 2026-11-10T10:17:01Z
- Identidad de firma
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Firma
- Oficialapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:5e9450f993be21df92acc29be844b33bfdc4b53d3830e5e7e572fde1a681a914
Referencia en esta versión
oci://hub.aggrega.ai/feature/core/concurrency-limit:1.0.0- Se aplica a
- dataplane.aggrega.ai/concurrency-cap
- Entra en conflicto con
- —
Parámetros del desarrollador
Valores que el desarrollador establece al acoplar esta funcionalidad.
Extiende BaseComponents#/schemas/BaseFeatureParameter
Contrato de salida
Valores que esta funcionalidad publica para los consumidores.
No se declararon valores de salida.
Anotaciones
No se declararon anotaciones.
Relaciones
Aristas tipadas hacia y desde otras entidades publicadas. Una referencia sin un destino publicado se muestra como una arista rota en lugar de como un enlace.
Usa
- se aplica ase aplica a
dataplane.aggrega.ai/concurrency-cap
- $refextiende el esquema (values)
BaseComponents#/schemas/BaseFeatureParameter
Usado por
implementa
implementa
implementa
implementa