| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| Introducing Node Readiness Controller |
| |
| |
Kubernetes just dropped the Node Readiness Controller - a smarter way to track node health. It slaps taints on nodes based on custom signals, not just the plain old "Ready" status. The goal? Safer pod scheduling that actually reflects what’s going on under the hood.
It's powered by the NodeReadinessRule (NRR) API, which lets operators define custom rules tied to real infrastructure signals. Think of it as a DIY control panel for taints and node readiness. |
|
| |
|
| |
|
| |
| How Kubernetes Learned to Resize Pods Without Restarting Them |
| |
| |
| Kubernetes v1.35 introduces in-place Pod resizing, allowing dynamic adjustments to CPU and memory limits without restarting containers. This feature addresses the operational gap of vertical scaling in Kubernetes by maintaining the same Pod UID and workload identity during resizing. With this breakthrough, operators can now adjust resources on running Pods without the need for disruptive restarts, improving operational efficiency and flexibility in managing workloads. |
|
| |
|
| |
|
| |
| Why Kubernetes is retiring Ingress NGINX |
| |
| |
The Kubernetes Steering Committee is pulling the plug on Ingress NGINX - official support ends March 2026. No more updates. No security patches. Gone.
Why? It's been coasting on fumes. One or two part-time maintainers couldn't keep up. The tech debt piled up. Now it's a security liability.
What's next: Time to switch. Ingress NGINX just can't scale anymore. Modern ingress controllers are the way forward. |
|
| |
|
| |
|
| |
| CVE-2026-22039: Kyverno Authorization Bypass |
| |
| |
Kyverno - a CNCF policy engine for Kubernetes - just dropped a critical one: CVE-2026-22039. It lets limited-access users jump namespaces by hijacking Kyverno's cluster-wide ServiceAccount through crafty use of policy context variable substitution. Think privilege escalation without breaking a sweat. Isolation? Poof.
Bigger picture: This puts Kubernetes admission controllers back under the spotlight. They're powerful, sure. But that also makes them a shaky foundation for trust. Time to tighten RBAC and audit those policy validations like it actually matters. |
|
| |
|
| |
|
| |
| How GKE Inference Gateway improved latency for Vertex AI |
| |
| |
Vertex AI now plays nice with GKE Inference Gateway, hooking into the Kubernetes Gateway API to manage serious generative AI workloads.
What’s new: load-aware and content-aware routing. It pulls from Prometheus metrics and leverages KV cache context to keep latency low and throughput high - exactly what high-volume inference demands. |
|
| |
|
| |
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |