I won’t argue with the ups and downs of each technos, but I recently looked into docker swarms and it was all I expected kubernetes to be, without the hassle. And I could also get a full cluster with services restored from scratch in 30s. But I am obviously biased towards it, too :)

Kinda like blaming a President at war for not saying “thank you” to its “benefactor” (despite having done so numerous times), no?

I don’t like the approach of piling more things on top of even more things to achieve the same goal as the base, frankly speaking. A “local” kubernetes cluster serve no purpose other than incredible complexity for little to no gain over a mere docker-compose. And a small cluster would work equally well with docker swarm.

A service, even made of multiple parts, should always be described that way. It’s easy to move “up” the stack of complexity, if you so desire. Having “have a k8s cluster with helm” working as the base requirement sounds insane to me.

Just checked the part about self-hosting. While it’s probably possible to handle things with a less heavy approach, their only “easy to use” example right now is to have a full-blown kubernetes cluster at hand or run locally in the source directory. That’s a bit much.