Paweł Krupa

@jhwbarlow what are the values of `podMonitorNamespaceSelector` and `podMonitorSelector` in your Prometheus CR?

Kubernetes v1.17.6 is not supported as per https://github.com/prometheus-operator/kube-prometheus#compatibility

kube-prometheus project is about delivering monitoring stack based on prometheus. Logging as such is out of scope for the project.

I think we would like to have this as an example jsonnet file in `examples/` directory. Possibly with some documentation. Any takers for doing this? :)

What's the use-case for changing those values to 30m?

Historically we did not want to expose those flags as their usage is discouraged by upstream (prometheus). Take a look at similar request in https://github.com/prometheus-operator/prometheus-operator/issues/3724 Right now we are closely...

Is this happening during the application of ClusterRole? Specifically this one: https://github.com/prometheus-operator/kube-prometheus/blob/main/manifests/kube-state-metrics-clusterRole.yaml ?

That would make sense in the past. However, right now I think this would clash with [the idea of reusing CRD-defined fields in `defaults` and reducing additional fields](https://github.com/prometheus-operator/kube-prometheus/pull/1477). We could...

It seems your prometheus instance is overloaded (WAL replay?). We recently removed liveness probes in https://github.com/prometheus-operator/prometheus-operator/pull/3502. Next prometheus-operator version will include this and it should fix your issue. You can...

AlertmanagerConfig selector can be already included as: ```jsonnet alertmanager+: { alertmanager+: { spec+: { alertmanagerConfigSelector: { matchLabels: { alertmanagerConfig: $alertmanager.alertmanager.metadata.name }, }, }, }, } ```