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
What happened?
When we override the k8c.spec.cassandra.datacenters.datacenterName also enabling telemetry for monitoring, Prometheus is dropping the target due to selector label mismatch.
Did you expect to see something different?
Prometheus should be able to monitor the cassandra instance even with datacenterName override.
How to reproduce it (as minimally and precisely as possible):
Enable telemetry & override the datacenterName
Environment
K8ssandra Operator version: v1.15.0
Kubernetes version information:
Client Version: v1.28.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.1
What happened?
When we override the k8c.spec.cassandra.datacenters.datacenterName also enabling telemetry for monitoring, Prometheus is dropping the target due to selector label mismatch.
Did you expect to see something different?
Prometheus should be able to monitor the cassandra instance even with datacenterName override.
How to reproduce it (as minimally and precisely as possible):
Enable telemetry & override the datacenterName
Environment
Client Version: v1.28.3
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.29.1
kind cluster v1.29.1
Anything else we need to know?:
Selector used in SVC vs ServiceMonitor
Prometheus Target Empty
┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: K8OP-252
The text was updated successfully, but these errors were encountered: