Okay, right off the bat, the author is already giving himself answers: > Essentially, this means that it [k8s] will have fewer concepts and be more composition

Okay, right off the bat, the author is already giving himself answers: > Essentially, this means that it [k8s] will have fewer concepts and be more compositional. Well, that's already the case ! At its base, k8s is literally a while loop that converges resources to wanted states. You CAN strip it down to your liking. However, as it is usually distributed, it would be useless to distribute it with nothing but the scheduler and the API ... I do get the author's point. At a certain point it becomes bloated. But I find that when used correctly, it is adequately complex for the problems it solves.