41–50 of 216 posts
also : post paywall mirror https://archive.is/x9tB6
I've read this article now multiple times and I'm still not sure if this is just good satire or if it's real and they can burn money like crazy or some subtle ad for aws managed cloud services :)
To get to this point, someone must have fucked up way earlier by not knowing what they were doing. Don't do k8s kids !
So they made bad architecture decisions, blamed it on Kubernetes for some reason, and then decided to rebuild everything from scratch. Solid. The takeaway being what? Don't make bad decisions?
When they pulled apart all those kubernetes clusters they probably found a single fat computer would run their entire workload. “Hey, look under all that DevOps cloud infrastructure! There’s some business logic! It’s been squashed flat by the weight of all the containers and orchestration and serverless functions and observability and IAM.”
I don't think this is a fair comment. This happens sometimes but usually people go with Kubernetes because they really do need its power and scalability. Also, any technology can be misused and abused. It's not the technology's fault. It's the people who misuse the technology's fault ( ). ( ) Even here, a lot of it comes from ignorance and human nature. 99.9% of people do not set out to fail. They usually do the best…
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…
There are genuine reasons for running multiple clusters. It helps to sometimes keep stateful (databases generally) workloads on one cluster, have another for stateless workloads etc. Sometimes customers demand complete isolation so they get their own cluster (although somehow its ok that the nodes are still VMs that are probably running on shared nodes… these requirements can be arbitrary sometimes).
Can you elaborate on that? What does it do?
Or course they are. The original value proposition of cloud providers managing your infra (and moreso with k8s) was that you could fire your ops team (now called "DevOps" because the whole idea didn't pan out) and the developers could manage their services directly.
In any case, your DevOps team has job security now.
Earlier quoted context omitted.
I don't think this is a fair comment. This happens sometimes but usually people go with Kubernetes because they really do need its power and scalability. Also, any technology can be misused and abused. It's not the technology's fault. It's the people who misuse the technology's fault ( ). ( ) Even here, a lot of it comes from ignorance and human nature. 99.9% of people do not set out to fail. They usually do the best…
The pointy is most organisations reach for container orchestration before they attempt to build fast software on a single machine.
> DevOps Team Is Happier Than Ever Or course they are. The original value proposition of cloud providers managing your infra (and moreso with k8s) was that you could fire your ops team (now called "DevOps" because the whole idea didn't pan out) and the developers could manage their services directly. In any case, your DevOps team has job security now.
The original value proposition is false, and more and more are realising this.