Infrastructure
You set requests. You set limits. The pod still gets throttled — or killed. Not because Kubernetes is broken. Because most teams have the wrong mental model of what these two fields actually do. When you configure kubernetes resource requests vs limits, the assumption is a simple min/max pair — requests reserve resources, limits cap…
The VPA vs HPA decision is one of the most misunderstood choices in Kubernetes resource management. Most Kubernetes teams reach for HPA first. It’s visible, it’s familiar, and the CPU metric dashboard makes the decision feel obvious. When traffic spikes, pods scale out. When traffic drops, they scale back. The mental model is clean. The…
Kubernetes 1.35 made in-place pod resize stable. Most of the coverage stopped there. The narrative wrote itself: Vertical Pod Autoscaler finally works for stateful workloads. No more restarts. Enable InPlaceOrRecreate and let the autoscaler do its job. The restart tax is gone. That framing is accurate about one thing and misleading about everything else. In-place…
The Kubernetes Gateway API project is not forcing you to migrate away from Ingress NGINX. There is no hard cutoff date, no deprecation warning in your cluster logs, no upgrade blocker. The project has simply moved on — and that quiet, undramatic shift is exactly what makes it operationally dangerous. Ingress NGINX is no longer…
Kubernetes 1.35 in-place pod resize graduates to stable — and with it, six years of a hidden operational tax on stateful workloads comes to an end. If a container needed more CPU or memory, the only safe answer was a restart. That design made sense for stateless services. It was painful for everything else. Increase…
OpenTofu migration is not a licensing decision. It is a control plane migration — and treating it as anything less is the fastest route to a corrupted state file, a broken provider dependency, or an operating model gap that surfaces at 2am on a production deployment. The license change is the trigger. The migration is…
Kubernetes networking has historically been split across two layers: the Container Network Interface (CNI), which handles pod-to-pod connectivity and network policy, and the service mesh, which adds application-layer features like mutual TLS, traffic routing, and observability. For years the common architecture looked like this: The rise of eBPF-based networking has started to collapse these layers….
Why Sovereignty Is a Control-Plane Problem — Not a Marketing Feature Sovereign infrastructure and disconnected cloud architecture are not the same problem — but they share the same failure mode: a control plane that cannot survive without external reachability. For a decade, “hybrid cloud” was positioned as independence. In practice, it usually meant placing infrastructure…
Executive Summary Infrastructure as a Software Asset means treating your data center like a codebase. If you’re spinning up infrastructure with an API but then managing it with a CLI, you’re not really doing Infrastructure as Code. For years, people treated data centers like big rooms full of hardware. You are accelerating legacy IT without…
Deterministic Networking for AI Infrastructure: Engineering the System Backplane Deterministic networking is the infrastructure requirement that most AI cluster designs get wrong — not because the concept is misunderstood, but because it gets treated as a networking problem when it is actually a systems problem. In the legacy data center, networking was a best-effort transport…
