Showing Post From Operations
Kubernetes 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 moreReverse proxies in 2026: revisit NGINX, Caddy and HAProxy before you put another proxy in front of your app
Almost every web application we run has something sitting in front of it. A few virtual machines run the actual code, and one or two small servers in front of them accept HTTPS, keep certificates, spread traffic, hide a dead backend and write the access log.
Read moreContainer engines in 2026: revisit Docker Engine, Podman and containerd before you install another container daemon
On most teams, installing a container engine is the first thing done on a new machine and the last thing anybody thinks about.
Read moreDNS servers in 2026: revisit CoreDNS, PowerDNS and BIND 9 before you add another DNS record by hand
In most companies, somebody still adds internal DNS records by hand. A new database gets an IP address, an engineer logs in to the DNS server, types one line into a zone file or a web console, and saves.
Read moreConfiguration management in 2026: revisit Ansible, Salt and Puppet before you write another server setup script
Almost every team has one: a setup.sh or bootstrap.sh written for the first production server and grown every year since. It installs packages, edits configuration files with sed, creates users and starts services.
Read more