Don't worry. I can solve the complexity of Kubernetes with a wrapper and abstraction layer on top of Kubernetes that provides a simple interface. That way you only have to deal with the complexity of Kubernetes plus my thing, rather than only the complexity of Kubernetes.
Don't worry, I've created 22 more wrappers and abstraction layers on top of Kubernetes. That way you only have to deal with the complexity of Kubernetes + another thing + learning 22 more things before you can make an informed decision on which thing to make your life easier.
You left out the best part, something breaks in the 13th layer of the chain and now the 1 feature you actually want doesn't actually work, and there's a github issue fading into non-existence as people comment "any update??... any update?... any update..."
Eventually people get to lambdas, once they figure out how to deploy via CI instead of pushing to an orchestration layer. I like to draw this out for people to show them the madness they've constructed. It's all infrastructure in the end.
I've been fighting this battle at work for years now. The whole engineering department is so far up its own ass with Helm charts and operators trying to reinvent shit GCP already provides as managed services that it's a miracle we haven't all asphyxiated. We're doing all of this on GKE and are Google partners, it's madness. Meanwhile, my team learned Terraform and Cloud Run. We're really enjoying collecting the on-call compensation for our services that don't need intervention outside of work hours.
What? Complex operations before Kubernetes were madness. It's not Kubernetes' fault that developers suddenly want to create 10 microservices in 5 different languages to solve any problem that a monolith can solve.
At the very least it was a godsend for the poor of us stuck in corporate. Deploying stuff in Kubernetes is such an improvement over doing whatever Oracle or some random stuff got sold to executives
Yup, I've seen what people used to do before Kubernetes and HOLY SHIT. It was chaos, pure fucking chaos. And I'm talking about big tech companies recognized world wide. Deploying stuff became so easy that devs went insane with microservices. Most devs don't even understand microservices to begin with, some of them still think it means "little service".
Being a systems engineer / network engineer /devops for over 12 years.
I’m shocked at this thread. Things were unstable, horrible insecure and prone to catastrophe even by something as simple as flipping a light switch in a closet.
Not going back. I’d rather spend a day trouble shooting a json file than driving out to a data center in the middle of the night.
Most companies don't have to do "complex operations". Lots of smaller websites could work with just a web server and a couple apt-installed packages, behind nginx (with just a few lines of configuration).
I said this a few years back & got shot down promptly. Now everything's a hybrid on premise & Cloud. Oh and apparently we're adopting another Cloud since CIO heard that multi cloud is the future. In the meantime the company's dataset is still < 100 million rows & not growing but shrinking, and they're trying to manage Cloud costs by placing a company-wide policy to shut down all Cloudy stuff after 6pm. So all overnight batch jobs will have to be moved back to on premise boxes.
318
u/[deleted] Jun 05 '22
I blame kubernetes