[RHOCP 4] Prometheus target 'serviceMonitor/openshift-metallb-system/monitor-metallb-controller/0' has a error message 'server returned HTTP status 502 Bad Gateway'

Solution Verified - Updated -

Issue

  • Default Metallb Operator setup has no issue and Prometheus target for the Controller is Up. The issue is observed when trying to host the speaker on specific infra nodes, speaker pods are scheduled on the infra nodes with the specific taints applied, but Prometheus target has a failure with below error:

    server returned HTTP status 502 Bad Gateway

  • kube-rbac-proxy container in the metallb controller pod shows the below error:

    $ oc logs controller-xxxx -c kube-rbac-proxy -n metallb-system

http: proxy error: dial tcp 10.xx.xx.xx:7472: connect: connection refused

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content