Hacker News Reader

Comment by threeseed | Hacker News Reader

This comment is so odd it's actually doing my head in.

Google invented Kubernetes, Apple runs Kubernetes and previously was heavily into Mesos, likewise for Netflix. And I've seen a lot of Engineering tech blogs and worked on AWS for a decade and never have I ever seen anyone spinning up thousands of micro-VMs in that way.

Not only are there all sorts of account limits you would immediately hit and have to negotiate but the networking would be problematic to say the least.

Meanwhile you can spin up ECS, EKS, Fargate which allow you to run thousands of containerised apps without any headaches at all. Plus they support you having unique IAM roles for each container.

View on HN

You do not run EKS “with no headaches” compared to just running a service on EC2.

While ECS/Fargate is easier, it’s still not headache free and you’re not taking into account how many large enterprises run lots of commercial off the shelf software on VMs.

Kubernetes? You mean the container orchestration system where they forgot to add Multi-tenancy? And no, Namespaces are not Multi-tenancy...

https://www.vcluster.com/

What kind of multi-tenancy are you trying to solve that Kubernetes namespaces cannot?

The one that the community recognizes never been there in the first place...

"Multi-tenancy in Kubernetes: implementation and optimization" - https://www.cncf.io/blog/2022/11/09/multi-tenancy-in-kuberne...

"...As we can see from the above discussion, the sharing of Kubernetes clusters is not an easy task; multi-tenancy is not a built-in feature of Kubernetes and can only be implemented with other projects’ support in tenant isolation on both control and data planes. This has resulted in considerable learning and adaptation costs for the entire solution. As a result, we are seeing an increasing number of users adopt multi-cluster solutions instead..."

Kubernetes has a lot of limitations from a multi tenancy perspective.

It's functional, but I think it's not as polished as the rest of Kubernetes which is why Kubernetes has a multi tenancy SIG that spawned the hierarchical namespace controller (https://github.com/kubernetes-sigs/hierarchical-namespaces) and virtual clusters (https://github.com/kubernetes-sigs/cluster-api-provider-nest...)

Reply on news.ycombinator.com