-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TargetDown alert #190
Comments
|
|
DNS Looks good: $ oc rsh observability-alertmanager-0
Defaulted container "alertmanager" out of: alertmanager, config-reloader, alertmanager-proxy, kube-rbac-proxy
sh-5.1$ getent hosts observability-alertmanager-2.alertmanager-operated.open-cluster-management-observability.svc
10.128.11.126 observability-alertmanager-2.alertmanager-operated.open-cluster-management-observability.svc.cluster.local
sh-5.1$ getent hosts observability-alertmanager-1.alertmanager-operated.open-cluster-management-observability.svc
10.131.15.7 observability-alertmanager-1.alertmanager-operated.open-cluster-management-observability.svc.cluster.local
sh-5.1$ getent hosts observability-alertmanager-0.alertmanager-operated.open-cluster-management-observability.svc
10.130.12.5 observability-alertmanager-0.alertmanager-operated.open-cluster-management-observability.svc.cluster.local
sh-5.1$ getent hosts alertmanager-operated.open-cluster-management-observability.svc
10.130.12.5 alertmanager-operated.open-cluster-management-observability.svc.cluster.local
10.131.15.7 alertmanager-operated.open-cluster-management-observability.svc.cluster.local
10.128.11.126 alertmanager-operated.open-cluster-management-observability.svc.cluster.local
sh-5.1$ |
Restarting of the pod ( I get the feeling this is a bug. Looking at the service, it does not get a cluster IP assigned to it (compare to e.g. alertmanager-metrics, which targets the same pods). WDYT? |
/cc @DanielFroehlich
The text was updated successfully, but these errors were encountered: