undefined | Better HN

0 pointsgeocar4y ago0 comments

If you're talking about a hosted k8s like EKS or a toy/single-node k8s, in 2021, then nothing: k8s is much better.

But if you're on-prem, and have a tonne of metal and just arrived in 2014 via a time machine, swarm was so much simpler and simpler that if you were a sysadmin who already had their own scripts -- their own jenkins-powered IC and git-hooks that built and deployed -- whatever it is you were building -- then swarm looked like a nice gradual extension of that, and k8s looked more like starting over and admitting defeat.

0 comments

4 comments · 2 top-level

Spivak4y ago· 1 in thread

I mean k8s is basically an infra rewrite in any shop that was/is currently VM based. "Hey you know that fundamental unit of isolation you've built all your tooling around. Throw it all away."

Don't get me wrong, I would absolutely go with k8s on any greenfield project but there's a huge huge opportunity for someone to take everyone's VM orchestration tools and quietly and semi-transparently add k8s support for gradual migrations.

rrdharan4y ago

Isn’t that VMware’s entire pitch for continued relevance?

waspight4y ago· 1 in thread

I see your point there. I only work on the pod side, not touching any metal.

runlevel14y ago

There's still plenty of room for improvement, but managing a K8s cluster on-prem is miles better than it was in 2014.

j / k navigate · click thread line to collapse