API Gateway

Publish stable application routes with clear timeouts and traffic policies.

Routes connect a host to a service#

A gateway route matches a hostname and path prefix, then sends a request to a ready service endpoint. Route names remain stable across service revisions, so deployments do not require clients to discover new instance addresses.

apiVersion: universe/v1
kind: GatewayRoute
metadata:
  name: catalog-public
spec:
  host: catalog.apps.universe.example
  pathPrefix: /v1/
  service: catalog
  timeoutSeconds: 20
  rateLimit:
    requestsPerMinute: 600

Understand gateway responses#

Status	Meaning
404	No route matches the host and path
429	The route rate limit was reached
502	The upstream connection failed
503	No ready service endpoints are available

Retry with care#

Retries are disabled for non-idempotent requests unless the application implements an idempotency key. Keep upstream timeouts shorter than the caller’s total request deadline.