Showing Post From Kubernetes
Kubernetes multi-tenancy in 2026: revisit vCluster, Capsule and Kamaji before you hand another team its own cluster
Sooner or later a platform team gets the same request again. A product squad wants “its own cluster” because it needs to install an operator with cluster-scoped CRDs, a data team wants admin rights to try a new scheduler, and a customer-facing team asks for hard isolation because an auditor said so.
Read moreProgressive delivery in 2026: revisit Argo Rollouts, Flagger and PipeCD before you ship another big-bang deploy
A Kubernetes RollingUpdate feels safe because pods come up gradually and readiness probes gate traffic. For many services that is still fine.
Read moreKubernetes cost visibility in 2026: revisit OpenCost, Kubecost and Robusta KRR before you buy another FinOps tool or add another node
When the cloud bill jumps, many teams reach for one of two habits. The first is to add another node because some pods are Pending and nobody wants an outage.
Read moreBare-metal load balancers for Kubernetes in 2026: revisit MetalLB, kube-vip and Cilium LB IPAM before you expose another Service
On a cloud cluster, you write type: LoadBalancer in a Service and a minute later an IP address appears. On your own servers, the same line gives you a Service that sits in <pending> forever.
Read moreChaos engineering in 2026: revisit Chaos Mesh, LitmusChaos and Krkn before you break another thing in production on purpose
Most teams first meet chaos engineering as a slogan: break things on purpose. Somebody installs a chaos tool, deletes a few pods in staging, sees them come back and declares the platform resilient.
Read moreKubernetes storage in 2026: revisit Rook-Ceph, Longhorn and OpenEBS before you put another database on a persistent volume
Running stateless services on Kubernetes is routine now. Running state is where the calm ends. The moment a database or a file store asks for a PersistentVolumeClaim, somebody must answer: where do those bytes live, how many copies exist, and what happens when a node dies at 2 AM?
Read more