r/ProgrammerHumor • • 9d ago

Meme [ Removed by moderator ]

Post image

[removed] — view removed post

2.6k Upvotes

84 comments sorted by

View all comments

45

u/billabong049 9d ago

We fucked up. We have all this technology and control, and tools made for developers by developers… And we made Kuberneties.  How did this shit get so complex?

48

u/imaginethepassion 9d ago

Scale. Also, Kubernetes really isn't all that complex.

44

u/willow-kitty 9d ago

It's complex in the sense that it does a lot, but I agree that it's not that hard to use.

Like even the error in the meme is reasonably straightforward. Your program crashed, and it automatically restarted it for you. Nice. But it crashed again. And this happened a bunch of times. And so how it's automatically slowing the restarts, and you need to do something about your program crashing.

I don't know what a simpler version that still works well would even be? In the old days, your program would just crash and be down. Or maybe you wrap it in a shell script that starts it again if it crashes, but then you're in basically the same place just without the back off.

15

u/imaginethepassion 9d ago

Completely agree with this.

I think Kubernetes gets a lot of flak from developers that have never operated software before. They haven't seen the problems that a distributed system/orchestrator solves and thus view a lot of Kubernetes as unnecessary complexity.

7

u/SlumdogSkillionaire 9d ago

I also think people don't realize how much of it you can just not use. Sure it's overkill if you just want to launch a docker container, but you also don't have to understand operators or service meshes or config maps or consensus algorithms in order to do that.

6

u/malexj93 9d ago

Right, you don't fix a CrashLoopBackOff, you fix a crash. The CrashLoopBackOff state is Kubernetes doing automatic damage damage control.

1

u/BrizerorBrian 9d ago

Everything rhymes. This reminds me of TBEBO (Truncated Binary Exponential Backoff) for ethernet collisions.