k8s-prometheus-adapter VS kube-prometheus

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.

I'm deploying kube-prometheus-stack along with prometheus-adapter in my monitoring stack for custom metrics.

I would like to see if anyone deployed prometheus-adapter and kube-prometheus-stack together for monitoring?

For us it is saturation of CPU and thread pool. It's implemented by exposing metrics of the thread pool to prometheus and turning that into a custom metric. (see) Looking at scaling based on job queue length next.

If you are using Prometheus or kube-prometheus-stack, you will need https://github.com/kubernetes-sigs/prometheus-adapter We are using it to scale our Pods based on number of messages in RabbitMQ queue. There also a walkthrough on https://github.com/kubernetes-sigs/prometheus-adapter/blob/master/docs/walkthrough.md

A prometheus-adapter installation.

Prometheus adapter to get custom/external metrics from Prometheus instance into Kubernetes API.

I never tested this but you have customized metrics API if the value % is available should work from my point of view Check this here https://github.com/kubernetes-sigs/prometheus-adapter

CPU and memory might not be the right metrics for your application to make scaling decisions. In such cases, you can use HPA (or VPA) with custom metrics as an alternative. To use custom metrics for autoscaling, you can use a custom metrics adapter instead of the Kubernetes Metrics Server. Popular custom metrics adapters are the Prometheus adapter and Kubernetes Event-Driven Autoscaler (KEDA).

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