prometheus-operator VS charts

The project repository for Prometheus-operator can be found here, The repo defines the CRDs and the controller. You can follow this documentation for the installation. which will require the creation of metrics exporters, node exporters, scrape configurations, etc.

Personally I use kubernetes, k3s is kind of lightweight, with the Prometheus operator.

https://k3s.io/

https://prometheus-operator.dev/

Kubernetes is not for everyone and is far from perfect but you already use Docker and you seem to seek many features offered by Kubernetes.

I see that the operator is a community-run project. Does anybody have any experience (positive or negative) on running the operator itself? I wonder if it is more for multi-tenant Prometheus. For single tenant Prometheus collection, I guess the big gain is abstracting scrape config into ServiceMonitor and PodMonitor resources? Is there anything else that this makes much better?

But in all honesty if you’re on k8s you’re probably best served by the Prometheus operator. It’ll give you all that and more, easily.

Try some monitoring.

It’s a common pattern [1] how else can users override the child objects you’re controller creates?

1 https://github.com/prometheus-operator/prometheus-operator/b...

The Prometheus operator is this one https://github.com/prometheus-operator/prometheus-operator

At a minimum, you want to look at your metrics using the Prometheus Operator. You can write alerts for resource requests.

Prometheus Operator is an independent project from the Prometheus project. I know, it can lead to confusion. In the official README you can find short comparison. Basically, Prometheus Operator does what an operator should do - provides Kubernetes native deployment and management of Prometheus and related monitoring components like Grafana or Alert Manager.

I'm using this prometheus helm chart.

I did this using the incubator/raw chart ( https://github.com/helm/charts/tree/master/incubator/raw ), by creating a k8s Job.

I've installed Prometheus operator 0.34 (which works as expected) on cluster A (main prom)Now I want to use the federation option,I mean collect metrics from other Prometheus which is located on other K8S cluster B

So I am using the helm chart stable/traefik to deploy a reverse proxy to my cluster. I need to customise it beyond what is possible with the variables I can set for the template.

It may be that we just migrated to Bitnami's chart when the old "stable" chart was deprecated

Edit: I'm using Postgresql Stable Chart version 5.3.10

I'm using the official stable/prometheus-operator chart do deploy Prometheus with helm.

I am using using https://github.com/helm/charts/tree/master/stable/airflow helm chart and building v1.10.8 puckle/docker-airflow image with kubernetes installed on it and using that image in the helm chart,But I keep getting