Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

blog.stackademic.com

Post reply on HN
Print view View original

61–70 of 216 posts

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

#61

Post by motbus3 »

figassis wrote: post #18

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…

Exactly. You might want to have one cluster per environment so you can test your deployments and rollback plans

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

#62

Post by karmarepellent »

oblio wrote: post #59
karmarepellent wrote: post #51

Earlier quoted context omitted.

We ran only two (very small) clusters for some time in the past and even then it introduced some unnecessary overhead on the ops side and some headaches on the dev side. Maybe they were just growing pains, but if I have to run Kubernetes again I will definitely opt for a single large cluster. After all Kubernetes provides all the primitives you need to enforce separation. You wouldn't create separate VMWare productio…

Kubernetes upgrades? Don't those risk bricking everything with just 1 environment?

In theory: absolutely. This is just anecdata and you are welcome to challenge me on it, but I have never had a problem upgrading Kubernetes itself. As long as you trail one version behind the latest to ensure critical bugs are fixed before you risk to run into them yourself, I think you are good.

Edit: To expand on it a little bit. I think there is always a real, theoretical risk that must be taken into account when you design your infrastructure. But when experience tells you that accounting for this potential risk may not be worth it in practice, you might get away with discarding it and keeping your infra lean. (Yes, I am starting to sweat just writing this).

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

#63

Post by namaria »

ali_piccioni wrote: post #44
risson wrote: post #3

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?

It highlights a classic management failure that I see again and again and again: Executing a project without identifying the prerequisite domain expertise and ensuring you have the right people.

Well understanding the problem and finding competent people is hard, riding on tool marketing and hiring bootcampers to do as you say is easy.

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

#65

Post by spiderfarmer »

throwaway2037 wrote: post #24
geuis wrote: post #17

Oh boy. Please, please stop using Medium for anything. I have lost count of how many potentially interesting or informative articles are published behind the Medium sign-in wall. At least for me, if you aren't publishing blog articles in public then what's the point of me trying to read them.

> "Create an account to read the full story." Why is this required?

It's awkward to write that on this platform, but: venture capital.

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

#66

Post by ExoticPearTree »

Is there a non-paid version of this? The title is a little clickbait, but reading the comments here seems like this is a story that jumped on the k8s bandwagon, made a lot of terrible decisions along the way and now they're blaming k8s for everything.

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

#68

Post by suzzer99 »

throwaway92t2 wrote: post #40
throwaway2037 wrote: post #24

Earlier quoted context omitted.

> "Create an account to read the full story." Why is this required?

They are also misleading the users with that message. I signed up, but now I got a message that I have to upgrade to a paid account... If they had told me that from the start, I would not bother with creating an account at all. The message implies that a free account would be enough

Yeah that's a BS dark pattern that drops my opinion of the site to zero.

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

#69

Post by shudza »

geuis wrote: post #17

Oh boy. Please, please stop using Medium for anything. I have lost count of how many potentially interesting or informative articles are published behind the Medium sign-in wall. At least for me, if you aren't publishing blog articles in public then what's the point of me trying to read them.

https://paywallreader.com/

https://archive.ph/20241127075543/https://blog.stackademic.c...

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

#70

Post by torginus »

figassis wrote: post #18

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…

Because they have k8s engineers each of whom wants to put it on their resume that they designed and implemented a working cluster in prod.
Post reply on HN