Welcome to IT Drills
Read little, type a lot. This book teaches you the Kubernetes Gateway API the way you need it at a customer site: first with kind on your laptop, then on a highly available RKE2 cluster on Proxmox – with Envoy Gateway as the main tool and Cilium as a second implementation.
You know Ingress. That is exactly where we start: every day takes a piece of Ingress knowledge, translates it into Gateway, Route and Policy, and shows what you could previously only achieve with annotations.
The Training Rules
- Type, don’t copy. Every command once yourself.
- Compare with Expected. After every drill you see what you should get. If it differs, that is where the real lesson is.
- Status first. Before you debug
curl, you read the conditions of the Gateway and the Route. The Gateway API almost always tells you itself what is wrong. - Pass the checkpoint. Only when the check script shows nothing but ✔ do you move on.
- Solve the challenge on your own. First the hint, then the solution.
- Lab values stay in the lab. Lab CA, passwords, tokens: never use them in production.
Structure of Each Training Day
| Section | Purpose |
|---|---|
| Briefing | The essentials in a few bullet points |
| Drills | Commands with expected output |
| Checkpoint | Check script: did everything work? |
| Challenge | A task without instructions |
| Enterprise Note | What is different in production |
The Training Plan
| Part | Day | Unit |
|---|---|---|
| Ground | 0 | Build the training ground |
| A – Basics in kind | 1 | From Ingress to the Gateway API |
| 2 | First Gateway and HTTPRoute | |
| 3 | Filters: redirect, rewrite, headers, mirroring, timeouts | |
| 4 | TLS: cert-manager, HTTPS redirect, SNI, passthrough, BackendTLSPolicy | |
| B – Traffic management | 5 | Canary and blue-green |
| 6 | gRPC, TCP and UDP | |
| 7 | Multi-tenancy: allowedRoutes, ReferenceGrant, ListenerSet | |
| C – RKE2 on Proxmox | 8 | Build the cluster: OpenTofu, Ansible, RKE2 HA, Cilium |
| 9 | Gateways on RKE2: LB IPAM, Envoy Gateway, Cilium GatewayClass | |
| 10 | Envoy Gateway extensions: traffic and security policies | |
| D – Production | 11 | Observability: metrics, access logs, tracing |
| 12 | High availability, upgrades, conformance | |
| 13 | Ingress migration with ingress2gateway | |
| 14 | Competition: disaster drills | |
| Appendix | A | Cheat sheet |
| B | Final exam |
The Training Ground
Part A/B: laptop – kind "gw-lab" Part C/D: Proxmox – RKE2 (lab.internal)
┌──────────────────────────────────┐ ┌──────────────────────────────────────┐
│ cloud-provider-kind (LB IPs) │ │ rke2-cp-1..3 10.10.20.11-13 (etcd) │
│ ns envoy-gateway-system: │ │ rke2-wk-1..3 10.10.20.21-23 │
│ Envoy Gateway (Class "eg") │ │ API VIP 10.10.20.10 (kube-vip) │
│ ns infra: Gateway "web" │ ──► │ Cilium: kube-proxy replacement, │
│ ns shop: shop-v1, shop-v2 │ │ LB IPAM + L2 (.100-.120) │
│ ns payments: payments (gRPC) │ │ GatewayClasses "eg" and "cilium" │
│ *.gw.localtest.me, lab CA │ │ *.apps.lab.internal, lab CA │
└──────────────────────────────────┘ └──────────────────────────────────────┘
Parts A and B run entirely on your laptop. From Part C on, you need a Proxmox host with enough resources for six VMs (details on Day 8).
Tip: Tested with Gateway API v1.6, Envoy Gateway v1.9.2, kind 0.33 (Kubernetes 1.37) and cloud-provider-kind 0.12.0. If a field differs:
kubectl explainand the docs at gateway-api.sigs.k8s.io or gateway.envoyproxy.io.
The Companion Code
All files from this book are publicly available on GitHub: https://github.com/thomaszachmann/gateway-api-zum-anfassen. Day 0 shows how to get them.
Let’s go.
Thomas Zachmann, October 2026