Kubernetes Is an Operating System for Machines You Do Not Pet

Kubernetes is how you treat a pile of machines as one computer you will not ssh into for fun. I do not run it for Dark Heart Labs. mystic-bytes is Jekyll on GitHub Pages. The writing laptop is Fedora. NeuroShell is a Mac app. There is no cluster to pet, and I will not pretend a Deployment YAML would make the essays more true.

The idea is older than the logo. Google’s Borg paper described large-scale cluster management as a service: schedule work, isolate it, replace the machine without replacing the job.¹ Kubernetes is the public, API-shaped descendant of that stance.² Pods, schedulers, and desired state are the interface. The node is livestock.

Use it when the failure domain is “a rack,” not “my SSD.” Pages and a VPS are allowed to stay small. Orchestrators are for the fleet you refuse to name individually. I read the docs so I can talk to people who do run fleets. I do not owe the CNCF a Helm chart for a static site.

— JV · Dark Heart Labs.

References

Abhishek Verma et al., “Large-scale cluster management at Google with Borg,” EuroSys 2015. ↩
Kubernetes Documentation, “Kubernetes Components,” https://kubernetes.io/docs/concepts/overview/components/. ↩