The problem

Production traffic routing needs a clear relationship between the gateway, route rules, and the services receiving requests. The migration moved that routing configuration from legacy Ingress to Gateway API.

What I implemented

  • Migrated production traffic routing from legacy Ingress to Kubernetes Gateway API.
  • Replaced legacy routing configuration with centralized, namespace-aware HTTPRoute rules.
  • Parameterized HTTPRoutes alongside the other Kubernetes resources in the environment-specific Helm configuration.

The resulting system

Production routing uses Gateway API and HTTPRoute configuration with namespace-aware rules, replacing the legacy Ingress setup.

Design considerations

Gateway configuration and application routes have distinct responsibilities. Route matching and namespace permissions need to reflect the intended service boundaries.