Hi all!
I have a couple of months to create and deploy a small cluster for running docker containers.
The cluster will consist of 3 master nodes and some workers. When it is ready, it will consist of about 15 servers.
I have little experience with Docker (managing some containers on my home server), I have spent the last 4 or 5 weeks studying and testing with Kubernetes and I think it’s a little overkill for what it’s going to take. You run the risk of adding unnecessary complexity.
I am seeing that instead Docker Swarm seems easier to set up and manage.
To consider that I will be on my own to manage it.
What do you think?
Thanks!
I agree with this. I think single node or not the industry is moving towards Kubernetes for container orchestration. Docker has showed their evil intentions and it’s time to leave them in the past. Even podman has native kubernetes manifest support (albeit limited last i checked) as @[email protected] pointed out there’s good avenues to take if you want to avoid the complexities of kubernetes like k3s.
Is k3s good for production?
I’m more of a Kubernetes the Hard way kind of person, but I think it can be suitable for certain production workloads. I’d trust a production workload on it way more then Docker Swarm
We’re using it in production at my day job in a couple of places.
How is it about the reverse proxy like traefik? Are you using nginx ingress with k3s?
Sorry for the many questions! Thanks!
Yep, using ingress-nginx on k3s as well.
I honestly hate that I can’t just deploy docker compose files directly to kubernetes seamlessly, and instead have to translate them to manifests. I’d say that having to drop all of that existing configuration as well as not being able to easily copy docker-compose’s for random new software I find is the biggest blocker for me being able to actually commit to using kubernetes.