This PR aims to reduce learning curve and simplify UX by configuring prometheus instances shipped with tobs to gather all PrometheusRules, ServiceMonitors, PodMonitors, and Probes that are injected into the cluster. This way the observability platform can collect data from the whole cluster.
To opt-out a resource from being used by prometheus shipped with tobs, you need to label it with tobs/excluded label (value doesn't matter).
This PR is also disabling scraping metrics using prometheus label mechanism and forcing users to use prometheus-operator CRs. This should prevent data duplication in larger clusters and align us closer to kube-prometheus project (jsonnet one). Feature can be re-enable if needed by the user.
What this PR does / why we need it
This PR aims to reduce learning curve and simplify UX by configuring prometheus instances shipped with tobs to gather all PrometheusRules, ServiceMonitors, PodMonitors, and Probes that are injected into the cluster. This way the observability platform can collect data from the whole cluster.
To opt-out a resource from being used by prometheus shipped with tobs, you need to label it with
tobs/excluded
label (value doesn't matter).This PR is also disabling scraping metrics using prometheus label mechanism and forcing users to use prometheus-operator CRs. This should prevent data duplication in larger clusters and align us closer to kube-prometheus project (jsonnet one). Feature can be re-enable if needed by the user.
Checklist