Selfhosted

39251 readers

361 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Deciding between Kubernetes or Docker Swarm (lemmy.world)

submitted 1 year ago by bananess@lemmy.world to c/selfhosted@lemmy.world

23 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] anthr76@lemmy.kutara.io 5 points 1 year ago (2 children)

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 @rs5th@lemmy.scottlabs.io pointed out there’s good avenues to take if you want to avoid the complexities of kubernetes like k3s.

[–] bananess@lemmy.world 2 points 1 year ago (2 children)

Is k3s good for production?

[–] anthr76@lemmy.kutara.io 2 points 1 year ago

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

[–] rs5th@lemmy.scottlabs.io 2 points 1 year ago (1 children)

We're using it in production at my day job in a couple of places.

[–] bananess@lemmy.world 2 points 1 year ago (1 children)

How is it about the reverse proxy like traefik? Are you using nginx ingress with k3s?

Sorry for the many questions! Thanks!

[–] rs5th@lemmy.scottlabs.io 3 points 1 year ago

Yep, using ingress-nginx on k3s as well.

[–] mlaga97@lemmy.mlaga97.space 0 points 1 year ago

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.