charts VS helm-charts

Both of these examples seem pretty obvious and something you wouldn’t mess up, but as your chart grows, so does your values.yaml file. A great example is the Redis chart by Bitnami. I encourage you to scroll through its values file. See you in a minute!

💡  The full details of helm charts can be referenced in their associated GitHub Repository.

The actual reason that our pods are not coming up is found when we review the helm installation that we are trying to run. If you check the dependencies in the GitHub repository (https://github.com/bitnami/charts/blob/main/bitnami/drupal/values.yaml) you find out that persistent storage is enabled by default and set to 8Gi. Also, the helm package uses MariaDB and the database size is specified to a default of 8Gi, thus setting the minimum storage for this installation to be 16Gi.

We're using https://github.com/bitnami/charts/tree/main/bitnami/spark, but I have heard good things about https://github.com/GoogleCloudPlatform/spark-on-k8s-operator as well. Hudi should not need any long running deployments as per the docs https://hudi.apache.org/docs/0.5.1/deployment/#deploying

Bitnami has its own scaffolding published at https://github.com/bitnami/charts/tree/main/template

i love the bitnami charts, now i'm at the point i want to write my own helm chart. (Openshift UI for Kubernetes packaged as a helm chart) I try to use the same structure and stuff as bitnami. I look for an "template" which i can start similar to the helm command 'helm create'. Is there something like this?At the moment i do a lot of copy of paste of other bitnami charts but this is kind of annoying. s. Bitnami Common Library

To install etcd, you can refer to the official documentation and build a multi-node etcd cluster; you can also use the chart installer provided by Bitnami for etcd .

bitnami.com perhaps?

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

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.

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.

https://github.com/prometheus-community/helm-charts/tree/mai...

Good luck! It's a lot.

We are running the `kube-prometheus-stack` helm chart: https://github.com/prometheus-community/helm-charts/

The 2 most common approaches I have seen are kube-prometheus-stack and kube-prometheus..

A basic Prometheus setup is only a helm chart or ansible role away.

There are integration repos for configuration management like Ansible and Helm Charts that need maintainers/contributors.

Let's look at an excellent example of using those labels: the Prometheus Helm chart.