charts VS HomeLab

Spinning up workloads in kubernetes is much different than just spinning up a container in docker or even with docker compose. If someone has not already packaged it in a helm chart or some other kubernetes workload you'll have to develop one yourself. There are some nice library charts you can use as a base that should handle just about any random docker image you want to deploy. https://github.com/bjw-s/helm-charts/tree/main/charts/library/common there is also a repo of pre developed charts for common images. https://github.com/k8s-at-home/charts but be aware it was recently deprecated so it won't be receiving any updates.

Take a look at https://github.com/k8s-at-home/charts (recently deprecated but still a fantastic resource) - there are charts for the popular Arrs , tools, etc. You could deploy each chart individually into a namespace, or you could create yourself an "umbrella" chart which pulls in all the necessary charts as dependencies.

Library charts. A very thorough example can be seen here and usages of it here.

I'd submitted a helm chart at https://github.com/k8s-at-home/charts/tree/master/charts/stable/firefly-iii if you want to try out

I know /u/stefantigro means well but the way you are both doing the helm charts is not ideal, helm charts are meant to be shared, not as a means to install apps into your cluster from a local folder. While they can be, it's not a good pattern. Take the helm chart from here for example. This is a published helm chart you can install using the commands in the Readme and you only need to provide the configuration for your instance from the values.yaml file. You can take a look at the values I use for this helm chart here. You can also see I'm using an custom Sonarr image, this image is tailored to running in Kubernetes

There is a working Helm chart for k8s-at-home that should be a good starting point. The biggest hurdle I see is that homebridge can conflict with SCALE's mDNS service as seen in this linked post.

There's an actual helm chart published here.

Maybe you should checkout: https://github.com/k8s-at-home/charts

And if you are interested how I've done it: https://github.com/Michaelpalacce/HomeLab

Example of a service that is being backed up (see backup.velero.io/backup-volume): https://github.com/Michaelpalacce/HomeLab/blob/master/Helm/apps/uptimekuma/templates/deployment.yaml

So I've been trying to get botkube to work, but it seems to me like the helm chart documentation is outdated? I've been looking at the values and trying to make things work and it didn't really work for me.. https://github.com/Michaelpalacce/HomeLab/blob/master/cluster/homelab/apps/botkube/helmrelease.yaml is what I tried

And here is some documentation and specifics I've ran into. https://github.com/Michaelpalacce/HomeLab/blob/master/docs/Backups.md

Also for configuration storage and git, I recommend taking a gitops approach to things. You can checkup FluxCD2. Here is my repo for reference https://github.com/Michaelpalacce/HomeLab

A few suggestions and thinks I wish I knew when I started ( personal opinions incoming ): 1. Get a single well sized server ( I'd go for 8 cpus .. And like more than 16 gigs of ram and 250+ ssd, ideally m.2 nvme ). Don't bother with raspberry pis.. Check my profile for my previous post to see a comparison of raspberry pi cluster and a x86 cluster... 2. Install proxmox to do virtualization 3. The majority of People in this sub hate kubernetes and the minority is scared to speak, but install k3s on the vms you spin up, this way you can scale resources and not worry about some elaborate setup of which containers go to which node and how to setup tls offloading, load balancing and much much much more as kubernetes will handle it for you. ( bonus since you are a devops engineer so you are probably used to kube clusters ) 4. Use Velero to do restic backups to s3 for services that are critical like dbs and password managers etc. 5. Do everything with ansible or GitOps! My personal homelab is here: https://github.com/Michaelpalacce/HomeLab utilizing ansible, flux for GitOps and renovate to keep my services up to date ( note to say my cluster spin up isn't as nice as I want it to be since when provisioning I have a Dependency on some secrets which I do manually.. But this is only first cluster setup ) 6. Setup a VPN and administrative services on the raspberry pi you have lying around. Personally my VPN is on the router but if yours doesn't support it, do that. 7. After you are done setting everything up and you have a backup, format the drives and reinstall the vms and re set everything up. Document the process, write automation scripts until satisfied... I genuinely recommend you do this like 3 times...... 8. Vpn I guess a lot of people like wireguard or adguard home... Doesn't really matter as long as it's not open vpn and it supports multiple threads. 9. Setup nodered for some automation around your new home, you'll love it. 10. Firefly is amazing! 11. Make sure that your CSI ( Container storage interface ) supports replication. Keep 3 replicas of critical volumes! 11. If you need any help, don't forget to ask :) personally shoot me a dm and I'll do my best to help, but I'm sure most of us here would

I have my own repo: https://github.com/Michaelpalacce/HomeLab I'm using kubernetes and GitOps for me is achieved through Fluxcd2 and partially renovate.

Here is how I've done it: https://github.com/Michaelpalacce/HomeLab/blob/master/Helm/apps/postgresql/templates/postgresql.yaml