Networking and traffic

kgateway

1.What is kgateway ?

kgateway is a control plane that watches Gateway API resources and configures Envoy proxies to route traffic into your cluster.

Think "Ingress, but modern, with Envoy doing the work".

  • Formerly Gloo Gateway (OSS), made by Solo.io
  • CNCF Sandbox project (accepted 2025-03-04)
  • Control plane is Go, talks to Envoy over xDS
  • Default GatewayClass : kgateway
  • Latest stable seen : v2.4.7
Request flow Client LoadBalancer Service Envoy proxy Pod(one per Gateway) Service / Endpoints App Pods

2.kgateway on Gateway API

Why Gateway API, and who owns what : the Gateway API section. Here is what kgateway does with each object.

GatewayCreating one makes the controller deploy an Envoy Deployment plus a LoadBalancer Service. Tune the proxy with GatewayParameters.
Objectkgateway does
GatewayClassClass kgateway, made by the chart
ListenerEnvoy listener : port, protocol, TLS
HTTPRouteEnvoy routes, pushed over xDS
TrafficPolicyExtras, attached by targetRefs
ProtocolsHTTP, gRPC, TCP/TLS

3.Control Plane vs Data Plane

kubectlor GitOps
API serverstores objects
controllerwatch, translate
EnvoyxDS config

status flows back to the Gateway (Accepted, Programmed)

  • ControllerPod in kgateway-system.
  • EnvoyAuto-created per Gateway. Applies routes and policies.
In short : The kgateway controller turns Gateway API objects into Envoy config, and Envoy carries the traffic.

4.kgateway CRDs

All in group gateway.kgateway.dev, version v1alpha1.

apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata: {name: httpbin}
spec:
  parentRefs: [{name: http}]
  hostnames: ["www.example.com"]
  rules:
  - backendRefs:
    - {name: httpbin, port: 8000}
KindUse it for
GatewayParametersCustomize generated proxy
TrafficPolicyAuth, rate limit, CORS, retry, JWT
BackendLambda, static, GCP upstreams
BackendConfigPolicyUpstream TLS, health checks
HTTPListenerPolicyListener settings, access logs
DirectResponseFixed reply, no backend
GatewayExtensionReusable ext auth config

5.Handy Commands

CommandDescriptionExample
helm upgrade -i kgateway-crdsInstall kgateway CRDs chartGateway API CRDs firstGateway API CRDs first
helm upgrade -i kgatewayInstall the control planeget pods -n kgateway-systemget pods -n kgateway-system
kubectl get gatewayclassConfirm class kgateway existsget gatewayclass kgatewayget gatewayclass kgateway
kubectl get gateway,httproute -ACheck Gateways and routesget gateway http -n kgateway-systemget gateway http -n kgateway-system
kubectl get svc,deploy -n <ns>Find Envoy Deploy + Svcget svc -n kgateway-systemget svc -n kgateway-system
kubectl describe httproute <name>Read route statusdescribe httproute httpbindescribe httproute httpbin
kubectl get trafficpolicy -AList policiesget trafficpolicy -Aget trafficpolicy -A
Charts : <chart> is oci://cr.kgateway.dev/kgateway-dev/charts/kgateway-crds (and .../kgateway), with -n kgateway-system --version v2.4.7. Add --create-namespace on the first install.

6.Gotchas

  • Spell the class kgateway exactly or nothing programs.
  • Install Gateway API CRDs first.
  • Do not use ports 19000, 8082, 9091 for listeners.
  • Own CRDs are v1alpha1, so APIs can change.
  • Cross namespace backendRefs need a ReferenceGrant.
  • Route stuck ? Read HTTPRoute status first.
Good to know
  • Policies attach by targetRefs or label targetSelectors.
  • TLS certs are Secrets (cert-manager can issue them).
  • agentgateway is a separate Rust data plane for AI / MCP traffic.
  • Quickstart chart version can lag the newest release.
In short : Install the CRDs and chart, check the GatewayClass and route status, and keep an eye on those v1alpha1 policies.