Universal-Kubernetes-Helm-Charts
helm-charts
Our great sponsors
Universal-Kubernetes-Helm-Charts | helm-charts | |
---|---|---|
17 | 11 | |
101 | 473 | |
- | - | |
6.7 | 9.0 | |
20 days ago | 6 days ago | |
Smarty | Smarty | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Universal-Kubernetes-Helm-Charts
-
Dedpulication standards of Helm Charts values file for a global chart with subcharts for our app. What's the right way to only need to specify a value once?
I would point you to what I call the "Universal Helm Charts" and some examples of how to use them.
-
Monitoring many cluster k8s
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.
-
Best way of managing Helm?
You may want to check out some other of my Helm Boilerplates to explain and highlight how using subcharts works. This is a companion repo to my upcoming DevOps + Kubernetes book. You also might like to check out my set of open-source universal helm charts which are published in a helm registry right now that you can leverage and has many industry best-practices built into it, such as anti-affinity rules, pod disruption budgets, horizontal pod autoscaling, ingress, service support, etc.
-
How do you guys on Mac M1's get around the annoying port forwarding issues with k8s + docker?
References: I use docker and Kubernetes daily. I currently manage numerous clusters and maintain pipelines for hundreds of microservices as I type this. I've been converting microservices into Docker images for companies hundreds if not thousands of times by now over the last bunches of years. I am also an avid and passionate open-source evangelist and Kubernetes/DevOps consultant. I author some Kubernetes controllers such as the Volume Autoscaler and have a set of Open Source Helm Charts and I love to contribute code/fixes wherever I run into issues.
-
StatelessSet Resource Type ?
If it helps at all I have some universal helm charts that have a template for easily deploying your application as a deployment or statefulset. You will notice I don’t even have a daemonset chart because it doesn’t make sense to. https://github.com/DevOps-Nirvana/Universal-Kubernetes-Helm-Charts
-
Helm makes it overly complex, or is it just me?
See: Open-Source Universal Helm Charts See: Boilerplates of using Open-Source Helm Charts (as a sub-chart)
-
The Helmet is a Helm Library Chart that defines many chart templates like Deployment, Service, Ingress, etc which can used in other application charts.
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
- How do you guys manage your deployment pipelines?
-
Monthly 'Shameless Self Promotion' thread - 2023/01
A open-source set of Universal Helm Charts with tons of best-practices baked into it such as autoscaling, PDBs, labeling, and an standardized set of "universal" templates that allows you to pivot between templates easily (meaning, you can easily make a deployment into a Statefulset or a Cronjob). Yes, I need to add more documentation, I know. I'm busy :P
-
Creating Kubernetes Templates
Universal Kubernetes Helm Charts
helm-charts
-
Helm/kustomize/k8s installation for Lemmy server?
Honestly, just use the bjw-s app-template for it. It's not complex enough to warrant a from-scratch chart.
-
"helm crearte" command for bitnami charts/common Library?
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.
- A k8s media factory utilizing the *arr suite
-
TrueCharts Maintainers Rude?
What about your charts being a 1:1 copy of Bernd Schorgers' app-template, formerly kah-common?
-
Getting Started with Kubernetes Questions
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.
-
Where are folks getting their helm charts for the standard media server apps (*arr, nzbget, etc) now?
I'm using this chart - it's a swiss army tool for any self-hosted docker containers lacking own helm files.
-
The Helmet is a Helm Library Chart that defines many chart templates like Deployment, Service, Ingress, etc which can used in other application charts.
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).
- With the k8s-at-home helm chart repository no longer being maintained, what are people using instead?
-
How do you use ArgoCD ? mono/multi repo, secrets.
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.
- Best way to organize simple deployments
What are some alternatives?
Helm-Chart-Boilerplates - Example implementations of the universal helm charts
charts - TrueNAS SCALE Apps Catalogs & Charts
containers - My collection of container images
Packer - Packer is a tool for creating identical machine images for multiple platforms from a single source configuration.
jailmaker - Persistent Linux 'jails' on TrueNAS SCALE to install software (docker-compose, portainer, podman, etc.) with full access to all files via bind mounts thanks to systemd-nspawn!
eksctl - The official CLI for Amazon EKS
library-charts - ⚠️ Deprecated : Helm library charts for the k8s@home Helm charts
helm-promotion-sample-app - Sample application that is promoted from QA to Staging to Production
charts - ⚠️ Deprecated : Helm charts for applications you run at home
Chalice-PynamoDB-Docker-Starter-Kit - A starter kit with some boilerplate code for getting started making low-cost serverless applications in Python on AWS with a great local development setup via Docker Compose
helm-repo-example - Auto-updating Helm repository with GitHub Actions