helm-charts
hull
Our great sponsors
helm-charts | hull | |
---|---|---|
97 | 13 | |
4,629 | 150 | |
2.4% | 0.7% | |
9.7 | 7.6 | |
7 days ago | about 1 month ago | |
Mustache | Python | |
Apache License 2.0 | 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.
helm-charts
-
Multi-Cluster Prometheus: Scaling Metrics Across Kubernetes Clusters
Building upon Bartłomiej Płotka's insightful blog on Prometheus and its passthrough agent mode, this post dives into implementing multi-cluster Prometheus support. Notably, the official inclusion of support in the widely-used kube-prometheus-stack came with the release in July 2023, making it easier to extend Prometheus monitoring across clusters.
-
Hands On: Pull metrics into Kubernetes from anywhere and treat them generically with the Keptn Metrics Server
The first thing you'll need, of course, is at least one backend to store metrics. So install Prometheus now:
-
Kubernetes Ingress Visibility
For the request following, something like jeager https://www.jaegertracing.io/, because you are talking more about tracing than necessarily logging. For just monitoring, https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack would be the starting point, then it depends. Nginx gives metrics out of the box, then you can pull in the dashboard like https://grafana.com/grafana/dashboards/14314-kubernetes-nginx-ingress-controller-nextgen-devops-nirvana/ , or full metal with something like service mesh monitoring which would provably fulfil most of the requirements
-
Smart-Cash project -Adding monitoring to EKS using Prometheus operator
kube-prometheus-stack is a Helm chart that contains several components to monitor the Kubernetes cluster, along with Grafana dashboards Grafana Dashboards to visualize the data. This option will be used in this article.
-
K8s Monitoring Per Namespace
This one I highly recommend: https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack
- Is Prometheus the right tool for my use case here?
-
Do we have any Prometheus metric to get the kubernetes cluster-level CPU/Memory requests/limits?
We use kube-prometheus-stack for metrics and have added the K8s views dashboards from grafana-dashboards-kubernetes. You should check out the k8s-views-global dashboard. I believe it's just what you are looking for.
-
Alertmanager SMTP configuration
You should take a look at "kube-prometheus-stack". It not only includes prometheus, node-exporter and Grafana but also a ton of preconfigured alerts and dashboards. Will save you a lot of work!
-
How do I find / edit Prometheus configuration after deploying it on Kubernetes ?
Since their are different ways to install what exactly did you install? Vanilla charts , stack, operator? https://github.com/prometheus-community/helm-charts/tree/main/charts
-
Show HN: Homelab Monitoring Setup with Grafana
https://github.com/prometheus-community/helm-charts/tree/mai...
Good luck! It's a lot.
hull
-
When to start adopting helm?
If you are just starting out and decide to go with writing your own Helm Charts I'd like to suggest our HULL Helm Library Chart for that purpose.
-
Getting Started with Helm
With HULL we have proposed an alternative yet Helm based solution a year ago which that tries to do it upside down by first giving you a documented Kubernetes API style full access to each objects configuration. Only on top of that it provides you further advanced options to (re)introduce abstraction into the mix - only if you need them and they actually improve your configuration. Everything takes place in the values.yaml so there is no digging around in the templates folder and everything is in view.
-
HULL Tutorial 01: Introducing HULL, the Helm Universal Layer Library
The HULL library Helm chart provides a single common interface to specifying Kubernetes objects within Helm Charts. The interface itself is based on the Kubernetes API schema itself which is integrated as a JSON schema in the HULL chart. Since all objects are defined directly in the values.yaml under the hull key there is no need to create and maintain custom template files when creating objects with HULL, everything happens in the values.yaml.
-
HULL Tutorial 02: Setting up a Helm Chart based on HULL
Good, now proceed by creating a new empty HULL based Helm chart. The steps are documented here but you will create it from scratch here to understand what is needed.
-
HULL Tutorial 03: Integrating ConfigMaps and Secrets
As a reminder, the goal of this tutorial series is to demonstrate how to build Helm charts based on the HULL library chart by recreating the functionality of the original kubernetes-dashboard Helm chart with a HULL based chart from scratch. When you have followed the previous part of this tutorial on setting up a HULL base chart you have created a for now unconfigured Helm chart named kubernetes-dashboard-hull in the 02_setup subfolder of your working directory (we assume that's ~/kubernetes-dashboard-hull here). You can alternatively download the current chart state here and continue from there. Also you should have checked out and extracted the kubernetes-dashboard Helm chart to kubernetes-dashboard in your working directory because examining it will be frequently required.
-
HULL Tutorial 07: Configuring Advanced Objects
the ability to specify any CustomResource as a customresource object instance. For CustomResources you additionally need to specify the kind and apiVersion besides the free form spec of your object.
-
Why is Helm considered best practice?
We have built a Helm Library chart named HULL, it provides amongst other features full access to all defined objects and their properties at creation and deployment time. Think of it as an API to specify Kubernetes objects directly in a Helm charts values.yaml. If there is some functionality you want to add or use in a particular scenario you can just configure it and the Kubernetes objects are as you actually want them to be - every aspect can always be tuned at deploy time if needed without you having to get back to the chart creator via PRs, hack the chart or similar methods. All doable with Helm and the HULL library chart, no other tooling required!
-
Grafana Labs' Tanka is Awesome.
We actually proposed an alternative way to solve the problem if you are Helm with our Helm library chart HULL.
-
Does anybody else find Helm charts pretty useless?
It may be worthwhile to look at the recently added examles, these are more advanced chart values.yamls from products we are deploying this way. You can see it can be pretty concise to define your applications structure with HULL in comparison.
-
values.schema.json ignored for values referenced in configmaps? (Helm 3)
Downsides to this is that you would have to write out the full content of your config in the values.yaml and cannot use the templating capabilities any further. Within the values.yaml no templating is allowed (unless you base your chart on this library chart we have created ;) which may be a more advanced topic if you just got started)
What are some alternatives?
tanka - Flexible, reusable and concise configuration for Kubernetes
ytt - YAML templating tool that works on YAML structure instead of text
kube-thanos - Kubernetes specific configuration for deploying Thanos.
helm-secrets - A helm plugin that help manage secrets with Git workflow and store them anywhere
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
charts - Helm Charts for Chatwoot
kustomize - Customization of kubernetes YAML configurations
charts - HAProxy Ingress helm charts
pihole-kubernetes - PiHole on kubernetes
agent - This is the entrypoint repository for the Superblocks Agent Platform
pack - CLI for building apps using Cloud Native Buildpacks
library-charts - ⚠️ Deprecated : Helm library charts for the k8s@home Helm charts