Here is my source code. Run it on the cloud for me. I do not care how.
This is actually a radical notion of how software can best be developed, deployed, upgraded, observed, managed, and improved. It must be, because so often it emerges long after we’ve tried everything else first. The Onsi Haiku Test implies
- That there is a crisp, contractual boundary between folks who provide platforms and folks whose work will consume the platform
- That building software that handles other software is, for most developers, not the most urgent, most valuable work they could be doing
Kubernetes, by itself, does not pass the Onsi Haiku Test. The boundary between development and operation is unclear. Developers can’t walk up to a vanilla Kubernetes cluster, hand it raw source code, and get all the basic amenities of routing, logging, service injection, and so on. Kubernetes gives you a rich toolbox for solving the Test in your own particular way. But a toolbox is not a machine. It is a toolbox.