Back to updates

Gateway-Api - 1

2026 (8)

March (3)

azure: [In preview] Public Preview: Application routing with meshless Istio in AKS

Azure Updates

2026-03-24

Azure AKS preview introduces Application Routing with meshless Istio as a supported ingress migration path after ingress-nginx deprecation, without requiring a full service mesh. It is positioned around Kubernetes Gateway API support and Istio-based routing.

k8s: Announcing Ingress2Gateway 1.0: Your Path to Gateway API

Kubernetes Official Blog

2026-03-20

Ingress2Gateway 1.0 is a stable migration assistant for moving from Ingress to Gateway API, with expanded Ingress-NGINX annotation support and more detailed warnings for unsupported or lossy translations. The release emphasizes controller-level integration tests and safer migration workflows, including manual review, validation in a dev cluster, and gradual traffic shifting.

k8s: Announcing the AI Gateway Working Group

Kubernetes Official Blog

2026-03-09

Kubernetes has formed a new AI Gateway Working Group to define standards and best practices for Gateway API-based networking infrastructure tailored to AI workloads.

February (2)

k8s: Before You Migrate: Five Surprising Ingress-NGINX Behaviors You Need to Know

Kubernetes Official Blog

2026-02-27

Kubernetes will retire the community Ingress-NGINX controller in March 2026; this post lists five non-obvious routing/rewriting/redirect behaviors that can cause outages when translating to Gateway API unless explicitly replicated.

aks: Release 2026-02-08

Release notes from AKS

2026-02-17

AKS release 2026-02-08 adds new Kubernetes patch versions, expands regional availability for API Server VNET Integration, and introduces several security/behavioral changes plus multiple component/image updates.

January (3)

k8s: Ingress NGINX: Statement from the Kubernetes Steering and Security Response Committees

Kubernetes Official Blog

2026-01-29

Kubernetes Steering and Security Response Committees announced Ingress NGINX will be retired in March 2026. There will be no further releases, bug fixes, or security patches. Roughly 50% of cloud-native environments rely on it, so many clusters are at risk unless teams check and migrate; alternatives (Gateway API or third‑party Ingress controllers) are not direct drop‑in replacements and require planning and engineering time. There are about two months to prepare.

k8s: Experimenting with Gateway API using kind

Kubernetes Official Blog

2026-01-28

This guide shows how to run a local experimental Gateway API environment using kind and cloud-provider-kind. It walks through creating a kind cluster, running cloud-provider-kind (which provides a LoadBalancer and a Gateway API controller and CRDs), deploying a Gateway and an HTTPRoute, deploying a demo echo application, testing with curl, troubleshooting common issues, and cleaning up. The setup is intended for learning and testing only — not production.

k8s: Headlamp in 2025: Project Highlights

Kubernetes Official Blog

2026-01-22

Headlamp’s 2025 recap highlights major growth: the project joined Kubernetes SIG UI, absorbed many community contributions via the Linux Foundation mentorship, and shipped several UX and platform features — multi-cluster views, Projects for grouping resources, a taskbar/activities model, improved search and map, OIDC/auth improvements, Helm/App Catalog enhancements, plugin ecosystem growth (including an AI Assistant), and performance, accessibility, and security upgrades.

2025 (2)

November (2)

k8s: Ingress NGINX Retirement: What You Need to Know

Kubernetes Official Blog

2025-11-11

Kubernetes SIG Network and the Security Response Committee announced the retirement of Ingress NGINX. Best-effort maintenance will continue until March 2026; after that there will be no further releases, bug fixes, or security updates. Users are advised to migrate to Gateway API or another Ingress controller.

k8s: Gateway API 1.4: New Features

Kubernetes Official Blog

2025-11-06

Gateway API v1.4.0 (released Oct 6, 2025) advances Kubernetes service networking with three features promoted to Standard (BackendTLSPolicy, supportedFeatures in GatewayClass status, and named rule fields for Routes) and several experimental additions (Mesh/XMesh, default Gateways, and an ExternalAuth filter for HTTPRoute). The release also adds per-port TLS/client-certificate configuration to address connection coalescing security, introduces a couple of breaking validation changes, improves CI/docs, and is usable on Kubernetes >=1.26.