kube-prometheus VS cluster-monitoring

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

I've grabbed the Prometheus stack from carlosedp/clustermonitoring and was able to get that deployed into my cluster. That stack is fairly dated and is pulling some pretty old versions of some of the containers. I decided to see if I could get the stack upgraded to the latest version of the containers as a learning exercise, but I'm running into an issue upgrading kube-prometheus to release-0.10.

If you are running on arm this is a nice project to try. https://github.com/carlosedp/cluster-monitoring

Prometheus stack via Carlos Eduardo's phenomenal clustermonitoring repo, modified to account for some differences in my setup (NFS-based PVs, MetalLB already set up, ingress annotations)

The main thing that jumped out to me was this hard coded IP: https://github.com/carlosedp/cluster-monitoring/blob/a136833aaf364a8e76809a9dca789bb59e070677/manifests/ingress-grafana.yaml#L8