> Especially if you use something like k3s with SQL database
I'll admit I've never used K8s outside of work very much, so I can't really argue on that!
> What were you thinking of things to take into account for k8s over swarm? The main difference for me is k8s needs a hell of a lot more boilerplate yaml for doing basically anything.
I think that's a big one, yes. Stateful services (i.e. volumes) are also much easier to setup and understand with Docker Swarm - which is the same as Compose. The routing mesh[1] is also lovely. I didn't use the Kubernetes routing mesh at work because the infrastructure department didn't allow us to, why is one a reason I was arguing against it; we used a very powerful and complex system without profiting from one of its most powerful feature.
I'll admit I've never used K8s outside of work very much, so I can't really argue on that!
> What were you thinking of things to take into account for k8s over swarm? The main difference for me is k8s needs a hell of a lot more boilerplate yaml for doing basically anything.
I think that's a big one, yes. Stateful services (i.e. volumes) are also much easier to setup and understand with Docker Swarm - which is the same as Compose. The routing mesh[1] is also lovely. I didn't use the Kubernetes routing mesh at work because the infrastructure department didn't allow us to, why is one a reason I was arguing against it; we used a very powerful and complex system without profiting from one of its most powerful feature.
[1]: https://docs.docker.com/engine/swarm/ingress/