helm-charts VS Helm-Chart-Boilerplates

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.

I would point you to what I call the "Universal Helm Charts" and some examples of how to use them.

Shameless Plug: Here's one of my dashboards I made for Ingress-Nginx, which is my recommended border router/gateway into all the services. It adds deep robust metrics and configurability, and if you've got years of experience with Nginx also, it allows you rich complex customization via nginx's configuration structure via kubernetes annotations. Besides that I have open-source helm charts which are easy to use, boilerplates showing how to use them, a volume autoscaler to automatically resize your disks as they get full, and a blog where I share various of my experience which is a companion blog to my upcoming book of the same name. Hope this helps! Feel free to ask if you have any further questions.

Here is an example of a repo that uses an sub-chart: https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-apache-with-configmap-template/deployment

Use multi-values files with helm ALWAYS. Allowing an env-specific overlay to tweak your default values files. See: https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-echoserver/deployment/boilerplate-echoserver

Helm charts - https://github.com/DevOps-Nirvana/Universal-Kubernetes-Helm-Charts Example using helm charts as sub charts - https://github.com/DevOps-Nirvana/Helm-Chart-Boilerplates/tree/master/boilerplate-echoserver

Helm Chart Boilerplates are examples of usage of the above Universal Helm Charts to help people understand how to use them more, a stop-gap until I add more documentation

Helm Chart Usage Boilerplates (Examples of using these helm chart)

To help you on deploying your service, I've created open source generic/universal Helm Charts to make it easy to do the above. Here are the Universal Helm Charts and here's some boilerplate examples of using them. These built-in have support for HPAs, services, ingresses, etc, making it as easy as autoscaling.enable: true I haven't gotten around to documenting the helm charts yet, but there's lots of comments in the values.yaml file explaining everything.