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

161–170 of 216 posts

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

#161

Post by mdaniel »

sontek wrote: post #137

I'm interested in reading this but don't want to have to login to medium to do so. Is there an alternate link?

https://scribe.rip/i-stopped-using-kubernetes-our-devops-tea... works for any Medium backed blog, which is almost always given away by the URL ending in a hex digits slug

https://news.ycombinator.com/item?id=28838053 is where I learned about that, with the top comment showing a bazillion bookmarklet fixes. I'd bet dollars to donuts someone has made a scribe.rip extension for your browser, too

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

#162

Post by marcosdumay »

anthonybsd wrote: post #129
mrweasel wrote: post #96

Earlier quoted context omitted.

> Isn’t the point of kubernetes that you can run your entire infra in a single cluster I've never seen that, but yes 47 seems like a lot. Often you'd need production, staging, test, development, something like that. Then you'd add an additional cluster for running auxiliary service, this is services that has special network access or are not related to you "main product". Maybe a few of these. Still there's a long wa…

>Often you'd need production, staging, test, development, something like that. Normally in K8s, segregating environments is done via namespaces, not clusters (unless there are some very specific resource constraints).

You always want lots of very specific resource constraints between those.

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

#163

Post by InDubioProRubio »

karmajunkie wrote: post #156
rdsubhas wrote: post #128

I wouldn't trust the management of this team for anything. They appear totally incompetent in both management and basic half-brain analytical skills. Who in the heck creates a cluster per service per cloud provider, duplicate all the supporting services around it, burn money and sanity in a pit, and blame the tool. Literally every single decision they listed was to use any of the given tools in the absolute worst, in…

that tends to be the take on most “k8s is too complex” articles, at least the ones i’ve seen. yes, it’s complex, but it’s simpler than running true high availability setups without something like it to standardize the processes and components needed. what i want to see is a before and after postmortem on teams that dropped it and compare their numbers like outages to get at the whole truth of their experience.

Complexity is a puzzle and attracts a certain kind of easy bored dev, who also has that rockstar flair, selling it to management - then quitting (cause bored) leaving a group of wizard-prophet-whorshippers to pray to the k8 goddess at the monolith circle at night. And you can not admit as management, that you went all in on a guru and a cult.

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

#166

Post by fragmede »

kgeist wrote: post #83
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…

We have 1 cluster per region (3 regions: Asia, US, EU), multiplied by redundancy clusters = 6 clusters. Then we have test environments, around 20 of them: 20 clusters. Then there are 10s of clusters installed on customers' infra. So 47 clusters isn't really a huge/strange number.

Curious how the 20 test clusters differ by.

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

#167

Post by marcosdumay »

fireflash38 wrote: post #145
Havoc wrote: post #114

Earlier quoted context omitted.

Can’t fix organisational problems with yaml ;)

But can you fix them with templated yaml?

Just go fully functional document generation languages, make your world there, and forget about the organizational problems.

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

#168

Post by fragmede »

andix wrote: post #131
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…

Isn't one of the strategies also to run one or two backup clusters for any production cluster? Which can take over the workloads if the primary cluster fails for some reason? In a cloud environment the backup cluster can be scaled up quickly if it has to take over, so while it's idling it only requires a few smaller nodes.

You might run a cluster per region, but the whole point of Kubernetes is that it's highly available. What specific piece are you worried about will go down in one cluster that you need two production clusters all the time? Upgrades are a special case where I could see spinning up a backup cluster for.

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

#169

Post by marcosdumay »

phendrenad2 wrote: post #125
threePointFive wrote: post #123

Does anyone have access to the full article? I'm curious what their alternative was. Terraform? Directly using cloud apis? VMs and Ansible?

> We selected tools that matched specific workloads: > Stateless services → Moved to AWS ECS/Fargate. > Stateful services → Deployed on EC2 instances with Docker, reducing the need for complex orchestration. > Batch jobs → Handled with AWS Batch. > Event-driven workflows → Shifted to AWS Lambda.

So... They outsourced their OPS?

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

#170

Post by [deleted] »

zelphirkalt wrote: post #80
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…

Maybe they had 47 different Kubernetes consultants coming in sequentially and each one found something to do different from the last one, but none of them got any time to update their predecessor's stuff.

[deleted]
Post reply on HN