Networking and traffic
kgateway
Extensions : kgateway (Envoy powered Gateway API, ex Gloo Gateway)
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
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.| Object | kgateway does |
|---|---|
| GatewayClass | Class kgateway, made by the chart |
| Listener | Envoy listener : port, protocol, TLS |
| HTTPRoute | Envoy routes, pushed over xDS |
| TrafficPolicy | Extras, attached by targetRefs |
| Protocols | HTTP, 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., 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}
| Kind | Use it for |
|---|---|
| GatewayParameters | Customize generated proxy |
| TrafficPolicy | Auth, rate limit, CORS, retry, JWT |
| Backend | Lambda, static, GCP upstreams |
| BackendConfigPolicy | Upstream TLS, health checks |
| HTTPListenerPolicy | Listener settings, access logs |
| DirectResponse | Fixed reply, no backend |
| GatewayExtension | Reusable ext auth config |
5.Handy Commands
| Command | Description | Example |
|---|---|---|
helm upgrade -i kgateway-crds | Install kgateway CRDs chartGateway API CRDs first | Gateway API CRDs first |
helm upgrade -i kgateway | Install the control planeget pods -n kgateway-system | get pods -n kgateway-system |
kubectl get gatewayclass | Confirm class kgateway existsget gatewayclass kgateway | get gatewayclass kgateway |
kubectl get gateway,httproute -A | Check Gateways and routesget gateway http -n kgateway-system | get gateway http -n kgateway-system |
kubectl get svc,deploy -n <ns> | Find Envoy Deploy + Svcget svc -n kgateway-system | get svc -n kgateway-system |
kubectl describe httproute <name> | Read route statusdescribe httproute httpbin | describe httproute httpbin |
kubectl get trafficpolicy -A | List policiesget trafficpolicy -A | get 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
kgatewayexactly 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
targetRefsor labeltargetSelectors. - 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.