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.
I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
141–150 of 216 posts
Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
#142I’ve been building software for 25 years across startups and giant megacorps alike, and I still don’t know what Kubernetes is.
Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
#143Why 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.
Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
#144So many astonishing things were done ... > As the number of microservices grew, each service often got its own dedicated cluster. Wow. Just wow.
Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
#145Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
#146Like 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…
Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
#147Each cluster is wasting tons of cpu and i/o bandwidth just to be idle. I was told that it is etcd doing thousands i/o per second and this is normal.
For a few monolith
Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
#148What a doozy of a start to this article. How do you even reach this point?
Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
#149Re: I Stopped Using Kubernetes. Our DevOps Team Is Happier Than Ever
#150How 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