SpinKube runs Spin WebAssembly apps on Kubernetes without containers, using a containerd shim and Kubernetes primitives. Pairing it with the Gateway API gives teams a cleaner, role-oriented way to expose WASM services without annotation sprawl.
Kubernetes SIG Network is retiring the ubiquitous Ingress NGINX controller in March 2026. Here’s how to inventory impact, choose a replacement, and migrate safely—ideally to Gateway API—without breaking traffic.
Envoy Gateway v1.7 lands with a dense set of Gateway API-adjacent upgrades: richer policy controls, better OTLP export options, safer extension defaults, and breaking changes that signal maturity.
Envoy Gateway v1.7 is another sign the Gateway API ecosystem is moving from ‘early adopter’ to ‘default’. We walk through what a v1.7-style platform setup looks like, plus common pitfalls in production.
ingress-nginx is heading into retirement in 2026. Here’s a practical, low-drama playbook to inventory your current usage, choose a target (Ingress controller vs Gateway API), and migrate with controlled risk.
Multiple fresh ingress-nginx CVEs are forcing teams to re-check a long-assumed ‘safe default’: the ingress controller. Here’s what the advisory says, what’s exploitable in real deployments, and a pragmatic patch + mitigation plan you can execute today.
Gateway API is the direction of travel, but teams still need an implementation that can survive production traffic. Envoy Gateway is quietly becoming that default. Here’s what’s maturing, what’s still sharp, and how to adopt it without breaking every app team.
