Showing Post From Kubernetes
Container 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 moreKubernetes packaging in 2026: revisit Helm, Kustomize and Timoni before you template another YAML file
Sooner or later every team on Kubernetes has the same argument. One person says Helm charts have become unreadable and the team should move to plain YAML with Kustomize overlays.
Read moreSelf-hosted CI in 2026: revisit Jenkins, Woodpecker CI and Tekton before you add another build agent
Most teams that keep builds on their own servers did not choose their CI engine recently. It was chosen years ago, by someone who may have left, on a machine that has been upgraded “when there was time”.
Read moreContainer sandboxing in 2026: revisit gVisor, Kata Containers and Firecracker before you run another untrusted workload
A normal container is a set of Linux processes with namespaces, cgroups, capabilities and a seccomp profile around them. That is a good packaging boundary and a reasonable resource boundary.
Read moreKubernetes backup in 2026: revisit Velero, K8up and Kanister before you trust another cluster restore
Most Kubernetes teams can rebuild a Deployment in two minutes. Fewer can say how long it takes to get back the data that Deployment was using.
Read more