Kubernetes is NOT a container orchestrator

#1

Post by moshloop » Mon, Feb 17, 2020, 2:07 PM UTC

Kubernetes is NOT a container orchestrator
flanksource.com

Re: Kubernetes is NOT a container orchestrator

#2

Post by parvenu74 » Mon, Feb 17, 2020, 2:51 PM UTC

Is there even a viable alternative to Kubernetes at this point? For that matter, is there an alternative to YAML for defining Kubernetes setups?

Re: Kubernetes is NOT a container orchestrator

#3

Post by mads » Mon, Feb 17, 2020, 2:53 PM UTC

parvenu74 wrote: post #2

Is there even a viable alternative to Kubernetes at this point? For that matter, is there an alternative to YAML for defining Kubernetes setups?

I find that nomad is actually a very good alternative.

Re: Kubernetes is NOT a container orchestrator

#4

Post by vkazanov » Mon, Feb 17, 2020, 2:53 PM UTC

How about "Kubernetes as a complexity generator"? :-)

Re: Kubernetes is NOT a container orchestrator

#5

Post by moshloop » Mon, Feb 17, 2020, 2:53 PM UTC

parvenu74 wrote: post #2

Is there even a viable alternative to Kubernetes at this point? For that matter, is there an alternative to YAML for defining Kubernetes setups?

Sure, https://github.com/Azure/draft doesn't require any YAML and deploys onto Kubernetes.

I remember someone also doing a demo of configuring your kubernetes deployment on your Java objects directly.

Re: Kubernetes is NOT a container orchestrator

#6

Post by MoroCode » Mon, Feb 17, 2020, 2:55 PM UTC

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

Re: Kubernetes is NOT a container orchestrator

#7

Post by throwaway3157 » Mon, Feb 17, 2020, 2:55 PM UTC

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

Re: Kubernetes is NOT a container orchestrator

#8

Post by moshloop » Mon, Feb 17, 2020, 2:56 PM UTC

vkazanov wrote: post #4

How about "Kubernetes as a complexity generator"? :-)

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.

Re: Kubernetes is NOT a container orchestrator

#9

Post by moshloop » Mon, Feb 17, 2020, 2:58 PM UTC

MoroCode wrote: post #6

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

You can solve container orchestration problems using Kubernetes, but you can also solve them using Swarm, Nomad and Mesos.

Kubernetes is the most popular, precisely because it is not over-engineered, the level of engineering matches the problem domain.

Re: Kubernetes is NOT a container orchestrator

#10

Post by bauerd » Mon, Feb 17, 2020, 2:59 PM UTC

moshloop wrote: post #8

vkazanov wrote: post #4

How about "Kubernetes as a complexity generator"? :-)

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.