Live data from Hacker News

Why Kubernetes is so complex

cloudplane.org

1–10 of 47 posts

Re: Why Kubernetes is so complex

#2
After reading TFA I don't feel enlightened. I don't think the author answered or even began to seriously address the question posed in the title; the discussion is approximately a beginner-level introduction to K8s Controllers.

A bit disappointed with cloudplane here.

Edit: @dollar - good one! Quite plausibly the case.

Re: Why Kubernetes is so complex

#3
post #2

After reading TFA I don't feel enlightened. I don't think the author answered or even began to seriously address the question posed in the title; the discussion is approximately a beginner-level introduction to K8s Controllers. A bit disappointed with cloudplane here. Edit: @dollar - good one! Quite plausibly the case.

Kubernetes is so complicated, the author got started describing it, then gave up and wandered off topic.

Re: Why Kubernetes is so complex

#4
I think the answer is hidden in the last paragraph. It was created by Google engineers to solve Google scale problems where they run maybe hunderds of thousands of services with a dedicated SRE team and massive tooling. For a small company, give me a way to run one container in an autoscable way and we can go from there.

Re: Why Kubernetes is so complex

#5
post #4

I think the answer is hidden in the last paragraph. It was created by Google engineers to solve Google scale problems where they run maybe hunderds of thousands of services with a dedicated SRE team and massive tooling. For a small company, give me a way to run one container in an autoscable way and we can go from there.

> For a small company, give me a way to run one container in an autoscable way and we can go from there.

What's the best way you've found to do that?

Re: Why Kubernetes is so complex

#7
post #4

I think the answer is hidden in the last paragraph. It was created by Google engineers to solve Google scale problems where they run maybe hunderds of thousands of services with a dedicated SRE team and massive tooling. For a small company, give me a way to run one container in an autoscable way and we can go from there.

> For a small company, give me a way to run one container in an autoscable way and we can go from there. What's the best way you've found to do that?

ECS/Fargate for long lived things. Lambdas for short lived things.

Re: Why Kubernetes is so complex

#8
post #4

I think the answer is hidden in the last paragraph. It was created by Google engineers to solve Google scale problems where they run maybe hunderds of thousands of services with a dedicated SRE team and massive tooling. For a small company, give me a way to run one container in an autoscable way and we can go from there.

Which is why kubernetes got adopted - everyone pretends they are Google, having Google problems, when they, in fact, don't.

Re: Why Kubernetes is so complex

#9
post #2

After reading TFA I don't feel enlightened. I don't think the author answered or even began to seriously address the question posed in the title; the discussion is approximately a beginner-level introduction to K8s Controllers. A bit disappointed with cloudplane here. Edit: @dollar - good one! Quite plausibly the case.

The article did feel half finished. Maybe it could be a series of articles, I suppose.

But jumping right to "Let's look at how Kubernetes works behind the scenes, and why the complexity may be a tradeoff worth making." this would be more useful to me. Specifically, like "why all the pieces" and comparing them to other solutions, which may be challenging.

Re: Why Kubernetes is so complex

#10
post #8
post #4

I think the answer is hidden in the last paragraph. It was created by Google engineers to solve Google scale problems where they run maybe hunderds of thousands of services with a dedicated SRE team and massive tooling. For a small company, give me a way to run one container in an autoscable way and we can go from there.

Which is why kubernetes got adopted - everyone pretends they are Google, having Google problems, when they, in fact, don't.

This is a heretical idea in some circles. Utter it and expect to be ostracized. In my case it’s cost a few job offers when I’ve suggested that a few python processes running under supervisor (e.g.) would be more than sufficient. It has its place but that point lies at a stage of development and sophistication far beyond where most cargo-cult users are currently.
Post reply on HN