Had some big outage because of… Scaleway ?
The egress for my K3S cluster is hosted there and was for some reason unavailable
I will have to track the logs, but not being able to login the main console to hard reboot the instance didn’t help
Time to bring that multi ingress dns rotating k8s operator project out of the forgejo limbo
#homelab #selfhosted #selfhosting #k3s #k8s #kubernetes #cloud #scaleway #outage #dns #ingress #egree
@whyhankee
A quite robust solution.
With its choice of the MicroOS (immutable server distro from openSuSE) as a host OS and a bit of configuration efforts of system-upgrade-controller and kured to automate the host and the kubernetes upgrades you may get a cluster that keep itself healthy and actual with relatively low effort.
I'd say it's easier to maintain than a AWS EKS one.
Caveats:
- learn Kubernetes concepts and cli management
Recommendations:
- hetzner k3s terraform config offers node groups, use small ARM instances for the control plane
- use S3(-like) storage to backup etcd (and Rancher) state, thus making your cluster recreatable from offsite state
- heterogenous cluster works and is cheaper, if your workload allows it
- enable Rancher or install it yourself, it's way better than UI in AWS/GCP
Feel free to ask me about it if you have some particular question.
It's time to learn about Kubernetes.
I know a tiny bit about K3S and managed to get a cluster of two machines running via Ansible Playbook, but I'm not familiar with it whatsoever.
However, I know this is an important tool and I need to learn how to use it so that's exactly what I'm gonna do.
If any of you can recommend tutorials or sites teaching it, I'd appreciate you writing it down in the comments.
#ansible #playbook #deployment #k3s #kubernetes #cluster #learning #sysadmin
I can finally receive, send and reply to and with emails of my own domain(s)
That took 7 years of self hosting, a lot of research and, admittedly, a SMTP relay for outgoing emails, because the extra work to maintain a proper IP reputation (among others) didn’t seem worth it (yet ?)
Using Stalwart helped, being on K3S didn’t…
All that’s left if properly hooking up Postgres, some storage engine and a k8s configmap to track the Stalwart configuration file
#selfhosted #selfhosting #kubernetes #homelab #k3s #networking #k8s #email #mail #smtp #stalwart #postgres
Nu e heimelaben min: to ~10år gamle stasjonær-PCa me #nixOS, tilkobla UPS, én gammel laptop me Bazzite, og én vps nedi oslo me nixOS.
De kjøra alle kubernetes i form av #k3s, som holdes i tøylan av #fluxcd.
nixOS tøyleholdes av #comin.
Kikk gjerne: https://codeberg.org/papiris/infra-cd og /nix-config
Neste bi å få opp monitorering så æ kan hold beire øye me krætturet, og offsite backup av nåkka slag.
Rop ut om du vil bi me på å lag ei gjensidig lagringsklynga basert på sjøldrifta S3: https://garagehq.deuxfleurs.fr
While I was away, I finally got NetBird back up and running, and damn it was hard but it’s worth the effort
Setting it up with PocketID for authentication was probably the most headachy thing I could’ve pulled off, but now that it’s done and stable, I ain’t touching it
If you are looking for a stable and fully self hosted Tailscale replacement, I highly recommend !
#tailscale #headscale #netbird #vpn #wireguard #selfhosted #selfhosting #homelab #pocketid #kubernetes #k3s
Paul Wijhenke
DocYeet 
gemelen
Špoljarević 
HoldMyType
papiris gjør antifascisme🌠
Andy Syrewicze
Hey Gus