built != run. not sure if I agree with OP on precise figures, but, if you're dealing with: - actually federated k8 infrastructure (distributed etcd, etc) - e

built != run. not sure if I agree with OP on precise figures, but, if you're dealing with: - actually federated k8 infrastructure (distributed etcd, etc) - enough system load that k8 is actually worthwhile and not 'cool' - user / dev requests - whatever background IT projects are going on (updates / new nodes, existing upgrades, testing new configs, etc) and you want: - 24x7 operations (or even stringent 8x5) - people to be able to use the restroom and take vacations and still have 1-2 sets of hands available 1 person doesn't quite cut it, because (s)he will quit eventually, and you will have nooone. dev-centric mentalities of 'it compiled, ship it, i made a new futuristic fancy feature aren't i amazeballs' often don't take into account real operational concerns, which i think is precisely the point in critiquing k8s here