gateway API
What to Expect From Kubernetes 1.36
Kubernetes 1.36 launches April 22, 2026, marking a major shift in networking as Ingress-Nginx retires in favor of the more scalable Gateway API. Key updates include bolstered Linux User Namespaces for better ...
Adrian Bridgwater | | admission control config, CloudNativeCon, cluster security, container isolation, Deployment Stability, DRA, Dynamic Resource Allocation, EKS, fat image anti-pattern, gateway API, ingress-nginx retirement, Karpenter, KubeCon Europe, Kubernetes 1.36, Linux user namespaces, LLM weights, manifest-based admission control, OCI artifacts, platform engineering, security patches, specialized hardware, taints and tolerations, upgrade risk, VolumeSource, WatchCache
Navigating the Ingress NGINX Sunset: Four Migration Strategies and How to Choose
Ingress NGINX reached end-of-life in March 2026. Explore four migration strategies—alternate controllers, forks, direct Gateway API migration, and dual-support controllers (e.g., Traefik Ingress NGINX Provider)—plus a three-phase audit→swap→modernize plan for zero-downtime transition ...
Emile Vauge | | configuration translation., controller fork, gateway, gateway API, HTTPRoute, ingress annotations, Ingress controller, ingress controller migration, Ingress NGINX, Ingress NGINX EOL, ingress-nginx-migration, IngressNightmare, kubernetes, Kubernetes control plane, Kubernetes networking, migration strategies, multi-tenant networking, observability, phased migration, production stability, security patches, Traefik Ingress NGINX Provider, zero-downtime migration
Service Mesh Evolution: Ambient Mode, Gateways & The Return of Simpler Architectures
Service mesh is evolving beyond sidecars. Ambient mode and Gateway APIs deliver security, observability, and traffic control with less overhead. Teams benefit from leaner, more flexible architectures ...
The Evolution of the Kubernetes Gateway API
The Kubernetes API plays a key role in the Kubernetes ecosystem, driving development, teamwork and creativity ...

