Gateway API
Purpose: For platform engineers, operators, application teams, documents the Envoy Gateway based gateway-api service in openCenter-gitops-base.
The gateway-api service deploys Envoy Gateway as the implementation for Kubernetes Gateway API resources.
What This Repo Deploys
-
Namespace/envoy-gateway-system -
HelmRelease/envoy-gateway-api -
Base values Secret:
envoy-gateway-api-values-base -
Optional override Secret:
envoy-gateway-api-values-override
When to Use It
-
You want Gateway API rather than legacy ingress-only routing.
-
You need shared edge infrastructure with delegated route ownership.
Key Integration Points
-
cert-managerusually provides TLS automation. -
MetalLB or a cloud load balancer provides external IPs.
Example
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: app
spec:
parentRefs:
- name: public
namespace: envoy-gateway-system
rules:
- backendRefs:
- name: app
port: 80
Configuration Surfaces
-
Service path:
applications/base/services/gateway-api/ -
Namespace:
envoy-gateway-system -
Flux object:
HelmRelease/envoy-gateway-api -
Source:
oci://docker.io/envoyproxy