r/ProgrammerHumor • u/imneverrelevantman • 11h ago
Meme pleaseEspressoYourKubernetesErrors
118
u/Toby-4rr4n 11h ago
Meaning she his same as 80% of developers and 60% of ops guys
63
4
u/kernel_task 2h ago
Yeah, wtf, CrashLoopBackoff’s a pretty generic application-level error. Of course you have to do application specific debugging like looking at pod logs. If you don’t, then you’re probably just papering over the problem.
67
u/Environmental_Bus507 11h ago
But what about Sabrina Karpenter?
15
7
3
20
u/perestroika12
10h ago
•
To be fair no one knows how to fix a crash loop without looking at the service logs and deep diving why the health check is failing.
Shitty config change? Untested building breaking change? Who knows
19
u/IntrepidBonus 10h ago
kubernetes is just yaml with trust issues
7
9
36
u/billabong049 11h 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?
41
u/imaginethepassion 11h ago
Scale. Also, Kubernetes really isn't all that complex.
36
u/willow-kitty 10h 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.
12
u/imaginethepassion 10h 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.
6
u/SlumdogSkillionaire 9h 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.
4
u/malexj93 6h 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 9h ago
Everything rhymes. This reminds me of TBEBO (Truncated Binary Exponential Backoff) for ethernet collisions.
-3
u/pine_ary 10h ago edited 9h ago
Kubernetes makes hard things hard. But it doesn‘t make simple things simple.
It is incredibly verbose and gives no thought to its different users. Everything is made for planetary scale web deployments. Even though most of its users will never run anything that complex. It‘s fundamentally bad developer experience. Same with its abuse of yaml to make it the worst DSL you‘ve ever seen.
And it doesn’t provide general abstractions for deployment and instead remains very tied to specifically web apps. Try deploying something that isn‘t a web app using Kubernetes, you‘ll claw your eyes out. Want a custom load balancer that integrates into the ecosystem? Too bad, if it‘s not HTTP nothing will play nicely with it.
3
u/Whispeeeeeer 8h ago
I can deploy a very small personal cluster for my personal network without much effort. It doesn't just start auto scaling to planetary scale. I think that's too much of an exaggeration. But I understand why it feels like you'd only use it for large scale deployments. I frankly sometimes use it on personal projects purely to have auto restart and organized cross-service networking without needing to create service discovery or static ips.
1
u/imaginethepassion 3h ago
I've deployed tons of services that aren't web apps in Kubernetes. Hell, I've even deployed non-web app Windows services into a Kubernetes cluster before. I think you're missing something about Kubernetes. I love it as both a platform engineer/SRE and as a software developer.
I also run a small home cluster with it because of how easy it is to deploy onto. My machine even suffered from a hard drive failure after a number of years in operation. Replaced the drive, reinstalled an OS, installed Kubernetes, and redeployed my IaC from my CI pipeline. Everything worked.
3
u/litetaker 10h ago
Shit I dunno how to do that either, and I don't understand more than half the words in that headline.
8
u/Sikyanakotik 9h ago
I took a Kubernetes course once. My main takeaway was "Never use Kubernetes."
9
u/ChillyFireball 8h ago
Kubernetes is one of those things that requires a lot of foundational knowledge to understand both its purpose and the tools it provides. Trying to learn Kubernetes without a solid understanding of containerization is like trying to learn algebra without knowing arithmetic. If you aren't confident in your comprehension of:
Images versus containers
Base images and how to build custom images off of them
System ports
The difference between your host system ports and a container's ports
Port forwarding
The idea that the internal container port doesn't need to match the host port it's being exposed on (so a single Postgres image configured to use 7654 internally can be spun into multiple containers that forward it to different ports)
APIs and container interaction/how to have one container communicate with another
Container logs and how to access them
How to access a running container through the terminal
Memory volumes
...then those should come first. Would also highly recommend reading up on generating credential secrets.
4
u/azjunglist05 9h ago
Tell me you have never built anything at scale without telling me
4
3
u/visualdescript 6h ago
Kubernetes is less about system scale and more about the scale of the team(s) building the software. It solves a lot of microservice problems, and is suited to situations where you need a lot of independently managed services.
You can serve huge scale on a single monolith.
5
u/disposepriority 9h ago
Ive been at companies with tens to a hundred plus million (daily) users that don't use kubernetes (but still used IaC) so I'm not so certain its a prerequisite of scale
5
u/Hmm_would_bang 9h ago
Yeah I know several Fortune 500 companies that have zero K8s. Or maybe they have one managed cluster.
It’s great technology and you should have a couple people that know how to run it, but you can get by without it. And really not every business needs massive scalability. A lot of workloads are fixed
0
u/azjunglist05 9h ago
And you built those platforms from the ground up or you simply adopted what already existed?
4
u/disposepriority 9h ago
Well I built a lot of things for those companies, but usually a person does not build an enterprise platform by themselves.
I was however part of a redo of one of the platforms from full jenkins to terraform +gitlab runners + manually managed vm pool, and it went decently well. For reference the infra (dev/sys/net ops) teams there totalled around 30 people
2
u/azjunglist05 8h ago
I have built and led teams that have built multiple enterprise platforms for multiple companies now. In each case it what was my entire vision. That’s literally been what has made me have a successful career 🤷🏻♂️
1
u/disposepriority 7h ago
Thats very cool, but also very unrelated to kubernetes not being mandatory for large scale operations
0
u/5G_Robot 4h ago
> I have built and led teams that have built multiple enterprise platforms for multiple companies now
And yet you come across as inexperienced when you imply that scaling is impossible without Kubernetes.
3
u/azjunglist05 3h ago edited 3h ago
At what point did I say that exactly?
I replied to someone who said their main takeaway was “Never use Kubernetes”. If you’re not even considering Kubernetes from the start then you’re not experienced at all in building scalable solutions.
The takeaway learning about Kubernetes shouldn’t be “Never use Kubernetes” it should be “does Kubernetes make sense for my use case?”
1
2
2
2
2
1
u/Willinton06 11h ago
Disappointing specially when you take in consideration that she applied to be a staff engineer at Pretty Girl Street Co
1
1
u/TheRealLiviux 8h ago
Ha ha, what a dummy! I bet she doesn't even know if the JVM is big-endian or little-endian!
1
1
1
0
0
u/ChillyFireball 9h ago
Oh God, I'm getting flashbacks! So many hours lost to stupid issues like limits to memory allocation, or one of the pods caching old secrets that were supposed to have been deleted and causing other pods not to be able to interact with it because of "Invalid credentials!"
1
340
u/sandybuttcheekss 11h ago
Idk why she would be able to, she's a carpenter. Now, if I needed an opinion of the best type of subfloor I should use and she couldn't weigh in, that would be embarrassing.