If you’ve spent the last few years deploying applications to Kubernetes, you’re intimately familiar with the Ingress resource. It’s the trusty workhorse that gets HTTP traffic from the outside world into your cluster.

But let’s be honest: you’ve also felt the pain.

You want to do something seemingly simple, like split traffic for a canary release, rewrite a header, or do regex path matching. Suddenly, your clean YAML file is overflowing with a massive, unreadable block of controller-specific annotations.

“Wait, was the annotation nginx.ingress.kubernetes.io/rewrite-target or ingress.kubernetes.io/rewrite-target ?”

Enter the Kubernetes Gateway API . It’s not just a new tool; it’s a fundamental rethinking of how routing works in a cloud-native world.…