Here is the issue description from customer.

"we have 3 openshift-clusters (4.11) and all 3 are affected from the problem mentioned in https://access.redhat.com/solutions/6957936

we have the same scenario as mentioned in the redhat-article above: the metallb-speakers are configured to run only on our gateway-nodes. only difference is: we already use ocp4.11

metallb itself works fine, but the metrics-target for the service-monitor/monitor-metallb-controller returns "server returned HTTP status 502 Bad Gateway".

This issue has addrssed in the bug https://issues.redhat.com//browse/OCPBUGS-10024. Also it has fixed in OCP 4.11.32. But unfortunately customer is still facing the issue in ocp 4.11.32 as well. So creating a new bug for it.

NOTE: SFDC cae number: 03421758

1.
2.
3.