charts VS nomad-driver-containerd

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.

Could it be related to this? https://github.com/k8s-at-home/charts/pull/1435/files

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.

Author (https://github.com/Roblox/nomad-driver-containerd) here.

Not really, Podman and containerd are two different technologies, although both allow you to move away from Docker for various reasons (smaller CPU, memory footprint, better security etc). If you are invested into Red Hat container stack, podman makes more sense. However containerd is more universal.

K8s is already moving away from docker, and directly into containerd. Most recently they deprecated dockershim, and users now need to switch to containerd (since docker also uses containerd under the hood, and it doesn't make sense for the orchestration system to run a monolithic service like docker where it just need to launch the workloads)

Some reference links of k8s or PaaS build on top of k8s moving to containerd