Gloo Gateway
API gatewaygloo
Envoy-based Kubernetes ingress controller and API gateway on the Gateway API.
- Provider
- default
- Kind
- API gateway
- Category
- Edge
- Official docs
- https://docs.solo.io/gateway/latest/about/overview/
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| auth | enum | none | api-key | jwt | oauth2 | mtls | no | none | inherited |
| concurrencyLimit | boolean | — | no | false | inherited |
| edition | enum | open-source | enterprise | no | open-source | inherited |
| gatewayApi | boolean | — | no | true | inherited |
| idempotencyKeys | boolean | — | no | false | inherited |
| instances | integer | — | no | — | inherited |
| keyTtlHours | integer | — | no | — | inherited |
| managed | boolean | — | no | false | ▸ false |
| protocol | enum | http | grpc | websocket | fix | ouch | no | http | inherited |
| rateLimiting | boolean | — | no | false | ▸ false |
| tls | boolean | — | no | true | inherited |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
sync-chain-too-deep
Every consecutive synchronous hop from this entry point spends part of the stated p95 latency budget, and the chain's failures multiply. More than three hops is a budget nobody is tracking.
- — all of these hold:
- — the design requirement `latency.p95Ms` has a value
- — the longest chain of synchronous calls starting at the node is more than 3 hops long
nodes:
- { id: "gloo", component: "gloo" }API Gatewayalibaba-api-gatewayAmazon API Gatewayaws-api-gatewayAWS AppSync GraphQL APIaws-appsyncAzure API Managementazure-api-managementAI Gatewaycloudflare-ai-gatewayCloudflare API Shieldcloudflare-api-shieldMCP Server Portalcloudflare-mcp-portalCloudflare Privacy Gatewaycloudflare-privacy-gatewayGeneric API gatewayapi-gatewayApache APISIXapisixApollo GraphOSapollo-graphosEasegresseasegressEmissary-ingressemissaryEnvoy Gatewayenvoy-gatewayHasurahasuraHelicone AI Gatewayhelicone-gatewayHigresshigressKong GatewaykongKong AI Gatewaykong-ai-gatewayKong Konnectkong-konnectKrakenDkrakendLiteLLM ProxylitellmMartian GatewaymartianNot Diamondnot-diamondPortkey AI GatewayportkeyRequestyrequestySpring Cloud Gatewayspring-cloud-gatewayTyk GatewaytykUnifyunify-aiVercel AI Gatewayvercel-ai-gatewayWSO2 API Managerwso2-api-managerZuulzuulApigeeapigeeAgent Gatewaygoogle-agent-gatewayAPI Gatewaygoogle-api-gatewayApigee hybridgoogle-apigee-hybridCloud Endpointsgoogle-cloud-endpointsFirebase Data Connectgoogle-firebase-data-connectIBM API Connectibm-api-connectOCI API Gatewayoci-api-gateway
# yaml-language-server: $schema=../../schema/component.schema.json # Gloo Gateway: self-hosted Envoy-based Kubernetes ingress controller conformant with the Kubernetes # Gateway API. Per the product overview, local rate limiting, retries and timeouts are open source # while global rate limiting, JWT and external auth/OIDC need an enterprise licence, so all are opt-in. schemaVersion: "1" type: "component" id: "gloo" kind: "api-gateway" provider: "default" docs: "https://docs.solo.io/gateway/latest/about/overview/" defaults: managed: false rateLimiting: false properties: edition: type: "enum" values: ["open-source", "enterprise"] default: "open-source" gatewayApi: type: "boolean" default: true