med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

372
active users

#k3s

0 posts0 participants0 posts today
openSUSE Linux<p>When you're an <a href="https://fosstodon.org/tags/Island" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Island</span></a> away from major cloud providers, you improvise. Discover how a team in <a href="https://fosstodon.org/tags/Mauritius" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mauritius</span></a> built a distributed <a href="https://fosstodon.org/tags/K3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>K3s</span></a> <a href="https://fosstodon.org/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> cluster across the country from this <a href="https://fosstodon.org/tags/oSC25" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oSC25</span></a> talk. <a href="https://fosstodon.org/tags/EdgeComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EdgeComputing</span></a> <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openSUSE</span></a> <a href="https://youtu.be/3C4mAuK3FzY?si=jKdtyAZ8g-B9qeMc" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">youtu.be/3C4mAuK3FzY?si=jKdtyA</span><span class="invisible">Z8g-B9qeMc</span></a></p>
Benny<p><span class="h-card" translate="no"><a href="https://mastodon.social/@lucas3d" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lucas3d</span></a></span> second <a href="https://mastodontech.de/tags/PihHole" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PihHole</span></a> Instance is now running and setup as second <a href="https://mastodontech.de/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS</span></a> in my Network💪<br>Only concern is, that the second Instance is running in the same <a href="https://mastodontech.de/tags/K3S" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>K3S</span></a> Cluster as the first one, and it can happen that they run on the same node. Need to check how podAntiAffinity is working, never have used it before.<br>Or i will run it on one of the not used <a href="https://mastodontech.de/tags/RaspberryPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RaspberryPI</span></a> or the <a href="https://mastodontech.de/tags/ZimaBoard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZimaBoard</span></a> 2, which should arrive in some weeks.</p>
Mauricio Teixeira 🇺🇸🇧🇷<p>And why did I choose Talos Linux instead of k3s, minikube, or so many other ways to deploy Kubernetes? Very simple answer: immutable deployment + GitOps. I have a number of hosts that need to run apt/dnf update on a regular basis. As much as this can be automated, it is still tiresome to manage. I don't have to worry as much about an immutable host running a Kubernetes cluster, mostly because the bulk of the attack surface is in the pods, which can be easily upgraded by Renovate/GitOps (which is also something I miss on the hosts running Docker Compose).</p><p>Now the research starts. I know Kubernetes, but I don't know Talos Linux, so there's a lot to read because each Kubernetes deployment has it's own nitpicks. Besides, I need to figure out how to fit this new player in my current environment (CA, DNS, storage, backups, etc).</p><p>Will my experience become a series of blog posts? Honestly: most likely not. In a previous poll the majority of people who read my blog posts expressed that they're more interested in Docker/Podman. Besides, the Fediverse is already full of brilliant people talking extensively talking about Kubernetes, so I will not be " yet another one".</p><p>You will, however, hear me ranting. A lot.</p><p>3/3</p><p><a href="https://hachyderm.io/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HomeLab</span></a> <a href="https://hachyderm.io/tags/TalosLinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TalosLinux</span></a> <a href="https://hachyderm.io/tags/k3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k3s</span></a> <a href="https://hachyderm.io/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kubernetes</span></a> <a href="https://hachyderm.io/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a></p>
Rainer "friendica" SokollAngenommen ich habe einen Host miteinem halben Dutzend <a href="https://friendica.sokoll.com/search?tag=Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Docker</span></a> Containern. Ich hätte den Host (also eigentlich die Container) gerne hochverfügbar.<br>Welche einfachen Lösungen bieten sich an?<br>Kubernetes wäre scheinbar overkill.<br><a href="https://friendica.sokoll.com/search?tag=Rancher" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rancher</span></a>? <a href="https://friendica.sokoll.com/search?tag=K3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>K3s</span></a>? <a href="https://friendica.sokoll.com/search?tag=Portainer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Portainer</span></a>? Oder klassisch mit <a href="https://friendica.sokoll.com/search?tag=Linux-HA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux-HA</span></a> und <a href="https://friendica.sokoll.com/search?tag=DRBD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DRBD</span></a>? Oder ganz anders?
HoldMyType<p><a href="https://mathstodon.xyz/tags/k3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k3s</span></a> and <a href="https://mathstodon.xyz/tags/gitlab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gitlab</span></a> runner in a vm <a href="https://mathstodon.xyz/tags/devops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devops</span></a></p>
DocYeet :verified:<p>Back when I wrote those ansible playbooks, I thought it was a semi waste of time, hiding it under the "but I'm learning" excuse</p><p>But wow, I couldn't have been more wrong<br>This is the best thing ever<br>Coupled with the custom Debian ISO, and everything gets back up in approx 10 mins, without me doing anything</p><p><a href="https://mastodon.halis.io/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://mastodon.halis.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <a href="https://mastodon.halis.io/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>debian</span></a> <a href="https://mastodon.halis.io/tags/iso" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iso</span></a> <a href="https://mastodon.halis.io/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kubernetes</span></a> <a href="https://mastodon.halis.io/tags/k3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k3s</span></a> <a href="https://mastodon.halis.io/tags/ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ansible</span></a></p>
DocYeet :verified:<p>Finding of the night</p><p>When setting up my Proxmox VMs for Kubernetes, I set a template with 32Gb for the main storage, but turns out one of my hosts couldn't accommodate 32Gb per VM, but it still let the configuration go through because of the dynamic allocation</p><p>So now, I should be in bed, but I am trying to get those 2 k3s nodes back up and running so longhorn can rebuild everything during the night...</p><p>Rookie mistake past me, rookie mistake</p><p><a href="https://mastodon.halis.io/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kubernetes</span></a> <a href="https://mastodon.halis.io/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://mastodon.halis.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <a href="https://mastodon.halis.io/tags/longhorn" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>longhorn</span></a> <a href="https://mastodon.halis.io/tags/k3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k3s</span></a></p>
DocYeet :verified:<p>Today marks the first day my infrastructure shows all green since I started the original migration to k3s earlier this year</p><p>It has been a journey, and some other things are not green, but as far as things are going, data is safe, and uptime is reliable 👌 </p><p><a href="https://mastodon.halis.io/tags/k3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k3s</span></a> <a href="https://mastodon.halis.io/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://mastodon.halis.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <a href="https://mastodon.halis.io/tags/longhorn" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>longhorn</span></a> <a href="https://mastodon.halis.io/tags/kener" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kener</span></a> <a href="https://mastodon.halis.io/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.halis.io/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kubernetes</span></a> <a href="https://mastodon.halis.io/tags/uptime" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uptime</span></a> <a href="https://mastodon.halis.io/tags/migration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>migration</span></a></p>
DocYeet :verified:<p>I am trying to configure Owncast to share some Homelabbing during the day</p><p>The problem is, I cannot get OBS to connect to it, via its RTMP instance</p><p>Has anyone tried deploying Owncast on a Kubernetes cluster, and was successful ?</p><p>I checked online and very little resource...</p><p>Any help very much welcome</p><p><a href="https://mastodon.halis.io/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://mastodon.halis.io/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>selfhosted</span></a> <a href="https://mastodon.halis.io/tags/owncast" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>owncast</span></a> <a href="https://mastodon.halis.io/tags/kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kubernetes</span></a> <a href="https://mastodon.halis.io/tags/k3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k3s</span></a></p>

So my #homelab #k3s cluster suffered an outage I've been trying to recover from since yesterday.

The outage itself started 4 days ago, and I discovered it when I couldn't get back into the house:

#HomeAssistant was unresponsive and I couldn't open my garage door.

To make for "one of those mornings" I then also couldn't unlock my front door **with my keys**. No electronic locks involved, no keys behind the door...

The lock itself would unlock but the door latch wouldn't open.

Yeah. Fun.

Well, bugger. I seem to have accidentally entirely deleted #VictoriaMetrics from my #K3s cluster while converting it from hand-installed to Helm-managed.

It's a good job that there was nothing particularly important in it.

The problem I have now is that Longhorn is now stuck while provisioning a PV while bringing VM back up again.

I need some help from the #selfhosting and #homelab community, I have reached full analysis paralysis!

I have 3 weeks left to determine what hardware to buy for my #selfhosted #homeprod my goal is to run #nextcloud & #immich in production well enough that It can seamlessly support my wife to #degoogle

I was leaning towards #talos cluster or #k3s for #kubernetes and #longhorn storage, but might all be overkill

Have determined I have these options are similar price & energy budget points:

@neil I am still amazed every time I try to play some free mobile game somewhere outside my home how many ads I’m skipping thanks to #pihole !

Highly recommend this ^^ !

(In my case, it’s 3 pihole instances on a #k3s cluster powered by 3 raspberries).

Getting closer to installing actual usable services on the #K3s cluster. So far, I've got:

- Node Feature Discovery
- cert-manager
- Intel Device Plugins
- Specifically for GPU HW acceleration in Jellyfin, Immich, etc.
- Descheduler
- Longhorn

Next up is Authentik and then off to the races.

Second attempt to play with #kubernetes with 6 nodes #k3s running as VMs on my #proxmox. 3 masters with #kubevip and 3 workers with #longhorn (Kubernetes cluster storage)

So far, so good, but I haven't deployed any services yet. Thanks to Proxmox snapshots, which allow for easy reversion after mistakes

On my todo list: Backup on my Synology, Nginx,…

My plan is to test the migration of my services to k3s in this virtual environment. After that, I will gradually move to dedicated nodes
#homelab

Replied in thread

@arichtman yeah using overlay at scale does work it just requires a lot of planning and design. Ideally with some network engineers. My last experience was contrail, years ago, and it was not great.

I’ve used flannel and cilium for one-off personal things without issue. In fact #metallb worked really really well for me with #k3s in the past as well.