You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given a scrape class config such as the one below and setting the same scrape class in a PodMonitor service, only the relabelings are picked up by the resulting Prometheus job config, tlsConfig is ignored. Using the same scrape class in a ServiceMonitor works as expected.
Before this change, the TLS configuration from the scrape class wasn't
applied to the generated configuration for PodMonitor, ScrapeConfig and
Probe objects.
Closesprometheus-operator#6556
Signed-off-by: Simon Pasquier <spasquie@redhat.com>
Is there an existing issue for this?
What happened?
Description
Given a scrape class config such as the one below and setting the same scrape class in a PodMonitor service, only the relabelings are picked up by the resulting Prometheus job config, tlsConfig is ignored. Using the same scrape class in a ServiceMonitor works as expected.
Prometheus Operator Version
Kubernetes Version
v1.26.14-gke.1044000
Kubernetes Cluster Type
GKE
How did you deploy Prometheus-Operator?
yaml manifests
Manifests
No response
prometheus-operator log output
Anything else?
No response
The text was updated successfully, but these errors were encountered: