SIG Network announced Ingress2Gateway 1.0, a migration assistant that converts Kubernetes Ingress‑NGINX resources into Gateway API manifests. The release expands support to over 30 common NGINX annotations and adds extensive integration testing that validates runtime behavior across controllers. It also improves notification formatting, surfacing unsupported configurations and offering remediation guidance. The tool can be installed via Go, Homebrew, or binary download, enabling teams to safely transition before the March 2026 Ingress‑NGINX retirement.
The AI landscape is shifting from brief, stateless inference calls to long‑running, coordinated agents that require persistent state and secure execution. Traditional Kubernetes objects like StatefulSets struggle to manage thousands of singleton agents efficiently. The open‑source Agent Sandbox project introduces...
The Kubernetes image promoter (kpromo) was completely rewritten, shedding about 20% of its code and adopting a modular, seven‑phase pipeline. The nine‑step effort introduced adaptive rate limiting, clean interfaces, a dedicated pipeline engine, and native SLSA provenance, vulnerability scanning, and...
Kubernetes will retire the community‑maintained Ingress‑NGINX controller in March 2026, prompting users to migrate to alternatives such as Gateway API. The blog outlines five unexpected Ingress‑NGINX behaviors—case‑insensitive regex matching, global use‑regex impact, implicit regex from rewrite‑target, automatic trailing‑slash redirects, and URL...