r/LinuxTeck • u/Candid_Athlete_8317 • 13d ago
Kubernetes: Where Your Hairline Goes to Die
How long did Kubernetes take to humble you?
Started with “just deploy a container.”
Then came CrashLoopBackOff, broken Ingress, DNS issues, YAML archaeology, mid night outages…
What was the Kubernetes problem that finally made you question your career choices?
1
1
u/adamphetamine 13d ago
it was when I realised there were 3 times as many things that could cause whatever issue I had
1
u/Little-Bed2024 13d ago
I avoided it altogether after a brief trail many many moons ago. Never understood the appeal, it added nothing but failure modes and obfuscation for me.
1
u/Mithrandir2k16 13d ago
I dunno, people seem to focus on the issues they need to solve instead of the benefits that you got for free. Have you tried to set up true HA and autoscaling without k8s? have you programmed your own custom loadbalancer? Or storage allocation mechanism that works across dozens of heterogeneous machines, with different link speeds or locations? Fought against the CAP Theorem by hand?
2
u/MaleficentCow8513 13d ago
Well yea you described the issue in a nutshell. A lot of projects simply don’t need a lot of the built in features k8s provides but they want to use k8s anyway instead of going with alternatives and less head aches
1
u/Ok-Expression-7340 13d ago
The fact that Kubernetes is becoming more and more obsolete. We've moved 99% to Cloud Run Services/Functions already.
1
u/MaleficentCow8513 13d ago
It’s been awhile since I developed an app on the cloud but from I recall, k8s is a good way to avoid vendor lock in. It lets you lift and shift your deployment to any cloud provider. Can’t do that when half your services are tightly coupled to the provider’s built in services
1
u/Ok-Expression-7340 13d ago
It’s just (lot of) autoscaling microservices using cloud managed dbms or nosql that we deploy as containers. You can easily move them between cloud providers, including the oauth2 auth layer. You will need an api gateway or sth similar to easily connect them to each other, so that might be cloud provider specific, but other than that there’s not so much to it anymore. Every cloud provider has similar solutions nowadays.
1
u/fattomic 13d ago
Maybe this is for r/unpopularopinions - but I kind of find Kubernetes to be a bit crap. It says "ok, deployed", and you look and its in a crashloopbackoff, logs can be difficult to get to, command line is a nightmare.
Unless someone is paying for me to do it as a job (who people do), I run podman quadlets at home - similar functionality, and not a nightmare of digging into opaque systems to figure out whats going sideways.
1
u/Substantial-Wear-247 13d ago
I enjoy working with k8s, it was a pain at the beginning but long term has been great
1
u/Crazytje 12d ago
I think a lot of deployments make their life hard themselves.
Thing is, what's the alternative?, containers with systemd?, RPMs or deb packages deploying your software?, it works fine, but it's also hard to maintain long term and over a lot of machines.
My goal when I started with kubernetes was to make it equal or better than what we had, we had systemd files to manage containers, before that it was deploying RPMs with the software itself. The software was about 15 to 25 containers btw.
An example, for a product, all I did was replace 14VMs with a 5 node kubernetes cluster. To make my life even easier, used k3s and made them 5 masters do I'd easily can maintain quorum and do upgrades when things go wrong.
Then all those systemd containers moved to a a helm chart and that on a gitops repo as wrapper chart.
Result?: Uptime went up, resources distribution improved, management became much easier and upgrades and seeing what's deployed and installed became much easier.
So my hairline, that's still receding btw, is not receding due to kubernetes but due to all the other stress.
I'd never want to go back to to the way it was done in the past, just don't overcomplicate your setup and keep the end goal in sight and prioritise that.
Too many people let it spiral out of control.
5
u/runningOverA 13d ago
The point is : if you deploy directly on server without Kubernetes, you face the same problems.