helm-charts VS genericmediafactory

Honestly, just use the bjw-s app-template for it. It's not complex enough to warrant a from-scratch chart.

I just spoke with one of the k8s-at-home guys, and he hadn't heard of Helmet either, but he recommended this: https://github.com/bjw-s/helm-charts which has a bit more miles on it, formerly it was published as: https://github.com/k8s-at-home/library-charts – this is in thousands of charts, from what I can tell.

What about your charts being a 1:1 copy of Bernd Schorgers' app-template, formerly kah-common?

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.

I'm using this chart - it's a swiss army tool for any self-hosted docker containers lacking own helm files.

It seems to have some overlap with a similar library that has been developed over at the k8s-at-home community and later migrated to my personal repo: https://github.com/bjw-s/helm-charts/tree/main/charts/library/common (shameless plug :P).

It very much depends on how you structure and setup your applications. We always try to use Helm charts which means within each environment you have your Helm values and some generic stuff. In some cases we created kinda a blueprint chart which was generic enough to configure whatever we needed. A good example of that could be https://github.com/bjw-s/helm-charts. This keeps the „copy-pasting“ relatively organized and low effort.