-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
1.3.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When user alerts using separate Alertmanager, the workload alertmanager is https://alertmanager-user-workload.openshift-user-workload-monitoring.svc:9095. The korrel8r.yaml created by operator should include an extra domain for the User Workload monitoring.
Step to reproduced:
- Enable User Workload monitoring and use separate Alertmanager instance
- Deploy openshift-cluster-observability-operator and enable troubleshoot-panel.
- check the korrel8r.yaml generated by openshift-cluster-observability-operator
Actual Result:
#korrel8r.yaml stores: - domain: k8s - domain: alert metrics: https://thanos-querier.openshift-monitoring.svc:9091 alertmanager: https://alertmanager-main.openshift-monitoring.svc:9094 certificateAuthority: ./run/secrets/kubernetes.io/serviceaccount/service-ca.crt - domain: log ... - domain: metric ... - domain: netflow ... - domain: trace ...
Expected Result:
#the generated korrel8r.yaml include second alert domain using alertmanager-user-workload.openshift-user-workload-monitoring.svc:9095
stores: - domain: k8s - domain: alert metrics: https://thanos-querier.openshift-monitoring.svc:9091 alertmanager: https://alertmanager-main.openshift-monitoring.svc:9094 certificateAuthority: ./run/secrets/kubernetes.io/serviceaccount/service-ca.crt - domain: alert metrics: https://thanos-querier.openshift-monitoring.svc:9091 alertmanager: https://alertmanager-user-workload.openshift-user-workload-monitoring.svc:9095 certificateAuthority: ./run/secrets/kubernetes.io/serviceaccount/service-ca.crt - domain: log ... - domain: metric ... - domain: netflow ... - domain: trace ...