Swarm
guest@6admin.io:~$ ls ~/tags/swarm
The log driver that stopped the container from starting
A dirty power loss, a corrupted Swarm overlay, an internal DNS that no longer resolves and containers that refuse to start because their log driver cannot resolve a name. The anatomy of a cascade and why the real fault was elsewhere.
Kubernetes, or not
Kubernetes is rarely the right first choice. An honest tour of the floors below it: podman and quadlet on one host, docker-compose, Docker Swarm, then docker or podman with Nomad and Consul and the real threshold where Kubernetes finally earns its keep.
Hardening Docker Swarm
Hardening Docker Swarm: secrets, encrypted overlay network, node roles and the cluster's exposure surface.
Docker Swarm to Kubernetes: why I abandoned Swarm
Swarm works well for small deployments. But no rootless, no CSI, no autoscaling and a MACVLAN pinned to a single node: the four walls that forced the migration.
Scale-to-zero: Sablier wakes Swarm and Kubernetes on demand
Sablier wakes a sleeping container when someone knocks at the reverse proxy, then scales it back to zero. Scale-to-zero on Docker, Swarm and Kubernetes, with the real Traefik config, the two strategies and the true price of handing it the Docker socket.