From 277c5a43f39d1635c7234ccf1f867dbadf970e90 Mon Sep 17 00:00:00 2001 From: Surya Seetharaman Date: Thu, 2 Jul 2020 14:12:20 +0200 Subject: [PATCH] Bug 1851928: [metrics] TargetDown alert is always fired in ovnkube-node job The TargetDown alert was always getting fired for all the ovnkube-nodes because the metrics-bind-address flag was not getting passed in the exec command for the ovnkube-node container. This regression was introduced in PR #615. Prometheus was hence not able to scrape the up metrics. Signed-off-by: Surya Seetharaman --- bindata/network/ovn-kubernetes/ovnkube-node.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bindata/network/ovn-kubernetes/ovnkube-node.yaml b/bindata/network/ovn-kubernetes/ovnkube-node.yaml index 4fc53ce46a..f51c8f3dbc 100644 --- a/bindata/network/ovn-kubernetes/ovnkube-node.yaml +++ b/bindata/network/ovn-kubernetes/ovnkube-node.yaml @@ -131,7 +131,7 @@ spec: --sb-client-cacert /ovn-ca/ca-bundle.crt \ --config-file=/run/ovnkube-config/ovnkube.conf \ --loglevel "${OVN_KUBE_LOG_LEVEL}" \ - --inactivity-probe="${OVN_CONTROLLER_INACTIVITY_PROBE}" + --inactivity-probe="${OVN_CONTROLLER_INACTIVITY_PROBE}" \ ${hybrid_overlay_flags} \ --metrics-bind-address "0.0.0.0:9103" env: