[Taikonerd]

> If you need granular control over every tiny aspect of your container orchestration — network policies, pod scheduling, resource quotas, multi-tenant isolation, custom admission controllers, autoscaling on custom metrics — Kubernetes gives you knobs for all of it.

> The problem is that 99% of teams don't need any of those knobs.

I keep hoping for a Docker Swarm revival. It's the right size for small-to-medium-size deployments with normal requirements.

[nitinreddy88]

Every enterprise team (at least who are in B2B business) needs this. The number of security clearances (zero trust boundary), security compliance is must. May be in B2C space where you might not need that depending upon how secure you wanna be based on what data you hold

[NewJazz]

Yeah I was trying to give the post a serious consider, but the author just flatly dismissed network policies as not needed, suggesting that we just make new overlay networks for every set of containers that need to communicate. This post really doesn't resonate with me, even though I am on a small team using k8s in a small company.

[SOLAR_FIELDS]

ECS Fargate is basically this on AWS. It’s just not cloud agnostic. But Swarm itself while being cloud agnostic is a proprietary product as well, so you still get the lock in, just at a different layer

[denysonique]

Docker Swarm mode is part of Docker Engine released under Apache-2.0. No vendor lock-in.