Hacker News Reader

Comment by Aeolun | Hacker News Reader

Honestly, I find the reasons they name for using Kubernetes flimsy as hell.

“ECS doesn’t support helm charts!”

No shit sherlock, that’s a thing literally built on Kubernetes. It’s like a government RFP that can only be fulfilled by a single client.

View on HN

> We also encountered many smaller paper cuts, like attempting to gracefully terminate a single poorly behaving EC2 machine when running ECS on EC2. This is easy on Amazon’s Elastic Kubernetes Service (EKS), which allows you to simply cordon off the bad node and let the API server move the pods off to another machine while respecting their shutdown routines.

I dunno, that seems like a very good reason to me.

I assume that ECS Fargate would solve this, because one misbehaving ECS task would not affect others, and stopping it should still respect the shutdown routines.

Fargate is very expensive at scale. Great for small or bursty workloads, but when you’re at Figma scale, you almost always go EC2 for cost-effectiveness.

this isn't really true. It was very expensive when it was first released but now it's pretty cost competitive with EC2, especially when you consider easier scale down/up.

I think when you are at Figma scale you should have learned to keep things simpler. At this point I don’t think the (slightly) lower costs of EC2 weigh up against the benefits of Fargate.

To be fair there are many benefits of running on the platform that has the most mindshare.

Unless they are in this space competing against k8s, it’s reasonable for them if they want to use Helm charts, to move where they can.

Also, Helm doesn’t work with ECS, so doesn’t <50 other tools and tech from the CNCF map>.

I think what they should have said is "there isn't a tool like Helm for ECS" If you want to deploy a full prometheus, grafana, alertmanager, etc stack on ECS, good luck with that, no one has written the task definition for you to consume and override values.

With k8s you can easily deploy a helm chart that will deploy lots of things that all work together fairly easily.

recipes and tutorials say "helm" so we need "helm"

It's almost like people factor in a piece of software's tooling environment before they use the software - wild.

Reply on news.ycombinator.com