https://falcao.org/tags/gateway-api/Recent content in Gateway-Api on Danilo Falcão da SilvaHugoen-usThu, 21 May 2026 17:50:00 -0300https://falcao.org/posts/kubernetes-ingress-landscape-2026/Thu, 21 May 2026 17:50:00 -0300https://falcao.org/posts/kubernetes-ingress-landscape-2026/<p>For about a decade, &ldquo;Kubernetes ingress&rdquo; effectively meant one thing: <strong><code>ingress-nginx</code></strong>, the community-maintained controller that wrapped the Nginx engine behind the Kubernetes <code>Ingress</code> resource. It was fine. It was the default everyone reached for. It was also, quietly, the wrong long-term shape for the problem.</p> <p>That era ended in 2026. The community <code>ingress-nginx</code> project <strong>reached end-of-life in March 2026</strong>. The <strong>Kubernetes Gateway API</strong>, which graduated to GA on the v1.2 line, is now the forward-looking standard. <strong>Envoy Gateway</strong> is the CNCF reference implementation. <strong>Cilium</strong> does L7 routing in eBPF without a sidecar or an extra proxy. <strong>RKE2</strong> flipped to <strong>Traefik</strong> by default in v1.36 and removes <code>ingress-nginx</code> entirely in v1.37.</p>