kube-prometheus VS helm-charts

The last one is mostly an observability stack with Prometheus, Metric server, and Prometheus adapter to have excellent insights into what is happening on the cluster. You can reuse the same stack for autoscaling by repurposing all the data collected for monitoring.

kustomize Kube Prometheus

On the other hand, the Kube-prometheus project provides documentation and scripts to operate end-to-end Kubernetes cluster monitoring using the Prometheus Operator, making easier the process of monitoring the Kubernetes cluster.

For our load testing we’ve deployed Temporal on Kubernetes, and we’re using MySQL for the persistence backend. The MySQL instance has 4 CPU cores and 32GB RAM, and each Temporal service (Frontend, History, Matching, and Worker) has 2 pods, with requests for 1 CPU core and 1GB RAM as a starting point. We’re not setting CPU limits for our pods—see our upcoming Temporal on Kubernetes post for more details on why. For monitoring we’ll use Prometheus and Grafana, installed via the kube-prometheus stack, giving us some useful Kubernetes metrics.

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

- I'm missing a lot of the Grafana dashboards that are provisioned during the deployment, not sure why as it has worked before, and wanted to add them after install... I believe it's different ConfigMaps like the one in kube-prometheus but I was wondering if there's a way to force provisioning them all again at once (multiple k8s, node_exporter, vm, etc)?

Check out the kube Prometheus project -- https://github.com/prometheus-operator/kube-prometheus It's a bit heavy, but the included recording rules and dashboards give you a great start at understanding your cluster.

The actual link to the prometheus/grafana bundle: https://github.com/prometheus-operator/kube-prometheus

Here’s a list of what’s installed: https://github.com/prometheus-operator/kube-prometheus/tree/main/manifests

https://github.com/VictoriaMetrics/helm-charts/commit/128d2a7fa23c717e780655f03df83b03e3d637ac could be the reason

There is also victoriametrics-operator and victoriametrics k8s stack helm chart.

BTW, you can use victoria-metrics-k8s-stack as a drop-in replacement for kube-prometheus-stack.

It is possible to replace kube-prom-stack with VictoriaMetrics stack in every k8s cluster - see https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/README.md

I'm monitoring CPU, memory, disk, network usage etc, the basic stuff available from kubernetes metrics via api. I also have a sidecar pod to send CPU temperature via opentsdb endpoint of Victoria Metrics. I run this helm chart which has operator and db - it can be added to grafana as a Prometheus data source.

There is a k8s stack Helm Chart which can provide the same functionality. Also check VictoriaMetrics Operator docs and our guides .

For metrics there is VictoriaMetrics operator and helm chart, which can be used for monitoring Kubernetes. See this guide.