Selfhosted

49301 readers

590 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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

From Docker with Ansible to k3s: I don't get it... (sh.itjust.works)

submitted 1 day ago by sunoc@sh.itjust.works to c/selfhosted@lemmy.world

42 comments fedilink hide all child comments

Hey! I have been using Ansible to deploy Dockers for a few services on my Raspberry Pi for a while now and it's working great, but I want to learn MOAR and I need help...

Recently, I've been considering migrating to bare metal K3S for a few reasons:

To learn and actually practice K8S.
To have redundancy and to try HA.
My RPi are all already running on MicroOS, so it kind of make sense to me to try other SUSE stuff (?)
Maybe eventually being able to manage my two separated servers locations with a neat k3s + Tailscale setup!

Here is my problem: I don't understand how things are supposed to be done. All the examples I find feel wrong. More specifically:

Am I really supposed to have a collection of small yaml files for everything, that I use with kubectl apply -f ?? It feels wrong and way too "by hand"! Is there a more scripted way to do it? Should I stay with everything in Ansible ??
I see little to no example on how to deploy the service containers I want (pihole, navidrome, etc.) to a cluster, unlike docker-compose examples that can be found everywhere. Am I looking for the wrong thing?
Even official doc seems broken. Am I really supposed to run many helm commands (some of them how just fails) and try and get ssl certs just to have Rancher and its dashboard ?!

I feel that having a K3S + Traefik + Longhorn + Rancher on MicroOS should be straightforward, but it's really not.

It's very much a noob question, but I really want to understand what I am doing wrong. I'm really looking for advice and especially configuration examples that I could try to copy, use and modify!

Thanks in advance,

Cheers!

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

[–] atzanteol@sh.itjust.works 1 points 11 hours ago (1 children)

You're welcome to make whatever bad decisions you like. I can manage snaps with standard tooling. I can install, update, remove them with simple ansible scripts in a standard way.

Bash installers are bad. End of.

[–] moonpiedumplings@programming.dev 1 points 10 hours ago (1 children)

Canonical's snap use a proprietary backend, and comes at a risk of vendor lock in to their ecosystem.

The bash installer is fully open source.

You can make the bad decision of locking yourself into a closed ecosystem, but many sensible people recognize that snap is "of the devil" for a good reason.

[–] atzanteol@sh.itjust.works 1 points 3 hours ago (1 children)

You've made this about snap. Flatpak, rpm, deb, etc. all work too.

[–] moonpiedumplings@programming.dev 1 points 2 hours ago* (last edited 2 hours ago) (1 children)

Except k3s does not provide a deb, a flatpak, or a rpm.

[–] atzanteol@sh.itjust.works 1 points 1 hour ago

Ah - you have discovered my complaint.

That is precisely why I went with microk8s instead. I don't install software from people who can't be bothered to package their software using standard deployment tools which has been the correct way to distribute Linux software for decades.