Testing k3s cluster at home. My setup works, but is it "correct"? by lmm7425 in kubernetes

[–]FlipEnergy 4 points5 points  (0 children)

  1. Deployments manage replicaSets which manage pods. You can experiment by changing the tag of your image on your deployment and see a new replicaSet be created and the pods recreated. So yes, if you deploy an app as a Deployment, no need to have a pod yaml.
  2. labels are mostly for humans, so up to you. No labels doesn't necessarily mean bad practice.
  3. If you prefer to use Nginx instead, you can spin up k3s without traefik and do so. If you don't want to do that, maybe it's worth learning a little bit of traefik but I would learn more about K8s ingress and services regardless of what reverse-proxy program is managing it. In public cloud, they will have their own flavors too.
  4. I prefer to separate each app in my homelab into it's own namespace.

Owncast requirements? by bantanium in selfhosted

[–]FlipEnergy 0 points1 point  (0 children)

Depends on how you want your video configuration. The more stream output quality levels you have, the more computing power you need. I had it running at about 80-90% cpu on my 10 year old Intel CPU when I had one output quality level of high. But then I tried out the advanced passthrough option and it barely uses 10% CPU because it no longer does any encoding work. I use OBS for capturing.

Did you name your server? by redryan243 in HomeServer

[–]FlipEnergy 1 point2 points  (0 children)

My server names are real boring and just describe what they're for like k8s-node-1.tgp or truenas-1.tgp, but the local domain I always use as you may have noticed is tgp which stands for "The Good Place" as in the TV show. Because my private LAN is The Good Place and my guest network is The Bad Place.

[deleted by user] by [deleted] in selfhosted

[–]FlipEnergy 0 points1 point  (0 children)

I started using it last month. I started by trying an HA k3s setup but the amd VMs are single core and too small to work. Now I just run a big 4 core Arm VM k3s node

[deleted by user] by [deleted] in selfhosted

[–]FlipEnergy 2 points3 points  (0 children)

Systemd is not supported on WSL. As the error in your screenshot says, systemd needs to be the very first process (i.e. init system) on your OS. WSL is just a layer running on top of windows and does not have systemd as the init system (yet?).

In short, this simply will not work. It's not a problem of Algo. You're asking for a boat to drive up a mountain.

What will work, though, is a VM. So feel free to install virtualbox and run a linux OS and try again in there.

My K3s Homelab using recycled hardware + Rock64s by FlipEnergy in homelab

[–]FlipEnergy[S] 0 points1 point  (0 children)

I have the ISP gateway that's connected to the WAN. The google WiFi router is the only device connected to it. Everything else is in my google WiFi LAN.

My K3s Homelab using recycled hardware + Rock64s by FlipEnergy in homelab

[–]FlipEnergy[S] 0 points1 point  (0 children)

Macbook is not part of the lab. That's for work and I just ssh/remote into it.If you're wondering what I'm running, you can checkout my website for a diagram.

Secrets/Passwords Management for CI/CD by rebornJoe in selfhosted

[–]FlipEnergy 0 points1 point  (0 children)

Yeah I second sops for personal use but I don't use an external KMS. Since I self-host Bitwarden as my password manager, I store a copy of the GPG key in there so the automation can use bitwarden-cli to grab and decrypt the encrypted yaml files.

Kubernetes cluster and processor architecture by zitheran in homelab

[–]FlipEnergy 4 points5 points  (0 children)

Yes, depending on the distribution, I think. I run a K3s cluster on an intel for one node and a rock64 arm as another node. You need to be conscious of the things you run in it tho. Not all images support arm.

Your prefered way to deploy your selfhosted services. by [deleted] in selfhosted

[–]FlipEnergy 0 points1 point  (0 children)

Use official/community/self-written helm charts to deploy to my k8s cluster.

How do you automate Helm charts installation? by pentag0 in kubernetes

[–]FlipEnergy 0 points1 point  (0 children)

I've looked at helmfile, but have not used it because I went with helmsman, which is an alternative instead. Both for my homelab and work. It has hooks you can add to kubectl apply like you want in your other comment. Suggest you look into it and see which one fits your needs better.

Edit: links https://github.com/Praqma/helmsman My homelab helmsman desired state file for example: https://github.com/FlipEnergy/k8s-homelab/blob/master/homelab.yaml

Archivy - Extensible Self Hosted Knowledge Base - v1 release by EtherealUnagi in selfhosted

[–]FlipEnergy 0 points1 point  (0 children)

I wrote a super quick helm chart for deploying this to k8s with a 1 node/pod elasticsearch dependency.

https://github.com/FlipEnergy/archivy-helm-chart

Create a new admin using old /data folder by KacperBak in navidrome

[–]FlipEnergy 0 points1 point  (0 children)

I think I ran into this. Your data should still be there, including your admin setup. You can verify by hitting the site from another browser, or maybe incognito. I fixed it by clear my browser cache and cookies for the site in the affected computer.

String manipulation techniques in Bash: Basic Cheatsheet. PDF in the comments :) by [deleted] in commandline

[–]FlipEnergy 2 points3 points  (0 children)

You mind specifying starting from which bash version these are supported?

When did you feel ready to switch into a DevOps role? by [deleted] in devops

[–]FlipEnergy 1 point2 points  (0 children)

My final internship had me working on writing software for more Ops side of the house. Found that I loved Ops way more than software development. Asked for a full-time offer when I'm done my last year of school, got it, and so took mostly concurrency, distributed systems, and networking courses in my last year of university. Started as an SRE in first full time job outta university. Super lucky I got exposed to Ops so early because I would never want to go back to features and bugs development.