,
4 tweets,
1 min read
Read on Twitter
I am not deep in k8s land. But I do have a drive by observation: the API being coupled to kubectl, and the behavior of a workflow being tightly coupled, is a mistake we made early at Chef with Knife.
We started out being very explicit about workflow. What happened next is predictable: it was the wrong workflow for some folks. So we made it pluggable (good!), but then it was harder to maintain and less portable (need this plugin for our workflow, sorry!)
The core set of behaviors need to be reliable and declarative, and accessible reliably from the API. If you’re going to include workflow in that, the above still applies. It’s either in or out.
Halfsies gets you the downsides of every approach.
