Kubernetes
guest@6admin.io:~$ ls ~/tags/kubernetes
Do you need Kubernetes for a small team ?
A decision grid between full Kubernetes, provider-managed orchestration and an intermediate option, settled by the team's real ability to live with the stack rather than by technical fashion.
Bare-metal Kubernetes in HA, without kidding yourself
Standing up a highly available bare-metal Kubernetes cluster with no cloud at hand: k0s, an API VIP with no external load balancer, Cilium for the network and the LoadBalancer, Rook-Ceph for storage. Three pieces, not seven.
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 Kubernetes
Hardening Kubernetes: RBAC, PodSecurity, NetworkPolicy, secrets and the attack surface of a loosely scoped cluster.
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.
Twelve-Factor App: the Heroku method that survived containers
Adam Wiggins's twelve factors, written for Heroku in 2011, remain the best checklist for shipping an application as a service: config in the environment, stateless processes, dev/prod parity, logs as event streams, then their translation into containers and Kubernetes.