Live data from Hacker News

I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever

blog.stackademic.com

141–150 of 216 posts

Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever

#141

Why exactly did they have 47 clusters? One thing I noticed (maybe because I’m not at that scale) is that companies are running 1+ clusters per application. Isn’t the point of kubernetes that you can run your entire infra in a single cluster, and at most you’d need a second cluster for redundancy, and you can spread nodes across regions and AZs and even clouds? I think the bottleneck is networking and how much crossta…

It's just a matter of time before someone releases an orchestration layer for k8s clusters so the absurd Rube Goldberg machine that is modern devops stacks can grow even more complex.

karmada?

https://karmada.io/

Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever

#143

Why exactly did they have 47 clusters? One thing I noticed (maybe because I’m not at that scale) is that companies are running 1+ clusters per application. Isn’t the point of kubernetes that you can run your entire infra in a single cluster, and at most you’d need a second cluster for redundancy, and you can spread nodes across regions and AZs and even clouds? I think the bottleneck is networking and how much crossta…

It's just a matter of time before someone releases an orchestration layer for k8s clusters so the absurd Rube Goldberg machine that is modern devops stacks can grow even more complex.

https://istio.io/latest/

Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever

#145
post #114
post #31

Earlier quoted context omitted.

“We want to use one standard Helm chart for all applications but then we need it to support all possible variations and use cases across the whole company”

Can’t fix organisational problems with yaml ;)

But can you fix them with templated yaml?

Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever

#146
post #75

Like most tech stories this had pretty much nothing to do the tool itself but with the people/organization. The entire article can be summarized with this one quote > In short, organizational decisions and an overly cautious approach to resource isolation led to an unsustainable number of clusters. And while I emphasize with how they could end up in this situation, it feels like a lot of words were spent blaming the…

In my experience organizations that end up this way have a very much non blame-free culture. Can be driven by founders that lack technical skills and management experience but have a type-A personality. As a result no one wants to point out a bad decision because the person who made it will get reprimanded heavily. So they go down a path that is clearly wrong until they find a way to blame something external to reset. Usually that's someone who recently left the company or some tool choice.

Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever

#150
post #16

How to save 1M off your cloud infra? Start from a 2M bill. That's how I see most of these projects. You create a massively expensive infra because webscale, then 3 years down the road you (or someone else) gets to rebuild it 10x cheaper. You get to write two blog posts, one for using $tech and one for migrating off $tech. A line in the cv and a promotion. But kudos for them for managing to stop the snowball and actua…

To expand on this, I run BareMetalSavings.com[0] and the most common cause of people staying with the cloud is it's very hard for them to maintain their own K8S cluster(s), which they want to keep because they're great for any non-ops developer. So those savings are possible only if your devs are willing to leave the lock in of comfort [0]: https://BareMetalSavings.com

Cloud isn't about comfort lock in but dev efficiency.
Post reply on HN