4 ms·

Kubernetes appears to be continuing to increase in popularity despite a large number of these failure stories. Does anybody know why? What does kubernetes do th

Kubernetes appears to be continuing to increase in popularity despite a large number of these failure stories. Does anybody know why? What does kubernetes do that docker, AWS, Nomad, et al don't? And, if I'm stuck with kubernetes, is there an accepted "right way" to do kubernetes that will keep me from becoming a cautionary tale?

dilyevsky 4y ago
Bc these “failure stories” are nothing but run of the mill outages that anyone who runs distributed systems at scale has seen plenty of
IThoughtYouGNU 4y ago
Principal kubernetes consultant for a large firm here. Kubernetes uses Docker runtime so that eliminates your first question. AWS also uses Kubernetes, EKS is a modified version of Kubernetes, and most major companies do not use things like Nomad because they lack the ecosystem tooling that something like Kubernetes has. I think probably the best thing you could do to prevent issues like this is blue-green testing or proper integration testing with your infrastructure repository so you can roll back quickly when you realize that some change you made didn't work correctly. This is all in addition to significant amounts of it monitoring.
arinlen 4y ago
> What does kubernetes do that docker, AWS, Nomad, et al don't? Most of your comparisons are at best apples-to-oranges. For example, AWS also offers a managed Kubernetes service, which makes your comparison meaningless and just a keyword dump. Worse, AWS also offers its Elastic Container Service. Docker supports Docker swarm mode, which is easier to setup but inter-node communication is extremely slow and barely supports anything beyond launching containers. But to answer the question of why bother with Kubernetes, the answer is obvious: Kubernetes is the first coherent abstraction over heterogeneous clusters of COTS hardware, including networking, which just works and offers plenty of very useful features such as reversible deployment history. Deployments are entirely defined in code in a way that you can treat both deployments and infrastructure as cattle.
- chrisshroba 4y ago
  > you can treat both deployments and infrastructure as cattle. What does this analogy mean?
coding123 4y ago
Someone could just as easily make a website dedicated to failed react stories. ymmv on any tech.
notmelgibson 4y ago
ok123456 4y ago
Resume driven development. It's nothing new.

dilyevsky 4y ago

Bc these “failure stories” are nothing but run of the mill outages that anyone who runs distributed systems at scale has seen plenty of

IThoughtYouGNU 4y ago

Principal kubernetes consultant for a large firm here. Kubernetes uses Docker runtime so that eliminates your first question. AWS also uses Kubernetes, EKS is a modified version of Kubernetes, and most major companies do not use things like Nomad because they lack the ecosystem tooling that something like Kubernetes has. I think probably the best thing you could do to prevent issues like this is blue-green testing or proper integration testing with your infrastructure repository so you can roll back quickly when you realize that some change you made didn't work correctly. This is all in addition to significant amounts of it monitoring.

arinlen 4y ago

> What does kubernetes do that docker, AWS, Nomad, et al don't? Most of your comparisons are at best apples-to-oranges. For example, AWS also offers a managed Kubernetes service, which makes your comparison meaningless and just a keyword dump. Worse, AWS also offers its Elastic Container Service. Docker supports Docker swarm mode, which is easier to setup but inter-node communication is extremely slow and barely supports anything beyond launching containers. But to answer the question of why bother with Kubernetes, the answer is obvious: Kubernetes is the first coherent abstraction over heterogeneous clusters of COTS hardware, including networking, which just works and offers plenty of very useful features such as reversible deployment history. Deployments are entirely defined in code in a way that you can treat both deployments and infrastructure as cattle.

chrisshroba 4y ago
> you can treat both deployments and infrastructure as cattle. What does this analogy mean?

coding123 4y ago

Someone could just as easily make a website dedicated to failed react stories. ymmv on any tech.

notmelgibson 4y ago

ok123456 4y ago

Resume driven development. It's nothing new.