Kubernetes isn't the source of complexity - it is the problem domain of building and operating distributed systems that are fundamentally and essentially complex.
Compare the complexity of Kubernetes to Openstack - the next most similar project in the same problem space, and you will find Kubernetes is actually pretty simple.
OpenStack and Kubernetes serve different purposes. Despite the article, Kubernetes at its core really is a container orchestrator. OpenStack is a collection of software you'd use for running a mini-AWS on bare metal infrastructure.
My question is then what counts as a container orchestrator. Not to shit on the article but why over-complicate the definition of an already over-engineered system
Click bait title. The point of this article is that Kubernetes is indeed an orchestrator, but "so much more". However, it's mostly a bunch of random conversational pieces, like mentioning the slack channel has 90k users
The size of the slack channel alludes to the size of the eco-system, and the scale at which Kubernetes is solving not just technical coding problems, but non-technical communication problems
16 comments
[ 3.0 ms ] story [ 29.2 ms ] threadI remember someone also doing a demo of configuring your kubernetes deployment on your Java objects directly.
Compare the complexity of Kubernetes to Openstack - the next most similar project in the same problem space, and you will find Kubernetes is actually pretty simple.
Both fundamentally are about abstracting the way in which infrastructure is managed.
Kubernetes works with fully-fledged VM's as well - See Kubevirt
Kubernetes is the most popular, precisely because it is not over-engineered, the level of engineering matches the problem domain.