Showing Post From Kubernetes
Infrastructure access in 2026: revisit Teleport, Boundary and Warpgate before you hand out another SSH key
Every engineering team has an access story it does not like to tell. A new developer joins, and someone appends her public key to authorized_keys on fourteen servers by hand.
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 moreDistributed coordination in 2026: revisit etcd, ZooKeeper and Consul before you write another leader election
Most teams do not decide to build a distributed coordination system. It creeps in. A scheduled job runs on one VM.
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 moreRuntime security in 2026: revisit Falco, Tetragon and Tracee before you trust another runtime alert
Most teams now scan images before they ship and check manifests before they reach the cluster. Then the container starts, and for many of us the story stops there.
Read more