Paweł Krupa

I am actually curious now why `reloader_last_reload_successful` is not set to `0` when this happens. Especially since reload wasn't fully successful. :thinking:

It looks like you have a `cluster` label in one metric but not in the other. Does `container_cpu_usage_seconds_total{container!="POD",image!="",job="kubelet",metrics_path="/metrics/cadvisor", cluster!=""}` and `kube_pod_info{node!="",cluster!=""}` return any output?

It seems that your cluster is not configured correctly and you have `cluster` label attached to metrics from kube-state-metrics, but not to metrics from kubelet. You need to have it...

Nice job! Looks like something that would simplify my life few months ago 😅 I am curious what are the added benefits for using operator here instead of simple config...

Other lines were changed due to the automated jsonnet formatter on file save. I changed the PR to change only one line.

`fstype` selector is configurable. Setting is available in `$.values.nodeExporter.mixin._config.fsSelector: 'fstype!=""'`. I wonder if excluding `tmpfs` in the mixin can have some unpredicted consequences though :thinking:

This should be partially fixed when https://github.com/prometheus-operator/kube-prometheus/pull/1107 is merged. After that, we can fix part when it is automatically added with etcd addon.

`preferred_ip_protocol` is a global setting of a blackbox_exporter and as such it is not configurable on `Probe` level. You need to configure it with blackbox_exporter configuration file - https://github.com/prometheus-operator/kube-prometheus/blob/main/manifests/blackboxExporter-configuration.yaml#L12

blackbox-exporter deployed via kube-prometheus is using two different endpoints for two different things. On port named `https` we have blackbox exporter internal metrics and on `probe` port we have the...

I am marking this as help wanted in case anyone would like to contribute short documentation on the topic. Such a doc would be much appreciated!