[BUG] HTTPS_PROXY or HTTP_PROXY configured on the system breaks openshift-router

[mangelajo]

What happened:

If the system needs an HTTPS/HTTP proxy to connect outside of the local network and this is configured
on the system the openshift services will also try to use this proxy for contacting the board API server,
for example k8s api connects to OpenShift api to expose the OpenShift resources, this will fail.

listing oc get apiservices the router api will be offline.

What you expected to happen:

OpenShift router working normally, oc get apiservices to all resources online even when HTTP/HTTPS proxies are configured.

Environment:

• Microshift version (use microshift version):
• Hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

Relevant Logs

I0112 18:14:21.226488       1 template.go:437] router "msg"="starting router"  "version"="majorFromGit: \nminorFromGit: \ncommitFromGit: 9c9f9f42\nversionFromGit: 4.0.0-312-g9c9f9f42\ngitTreeState: clean\nbuildDate: 2021-10-18T17:15:38Z\n"
I0112 18:14:21.231297       1 metrics.go:155] metrics "msg"="router health and metrics port listening on HTTP and HTTPS"  "address"="0.0.0.0:1936"
I0112 18:14:21.265919       1 router.go:191] template "msg"="creating a new template router"  "writeDir"="/var/lib/haproxy"
I0112 18:14:21.266966       1 router.go:270] template "msg"="router will coalesce reloads within an interval of each other"  "interval"="5s"
I0112 18:14:21.280596       1 router.go:332] template "msg"="watching for changes"  "path"="/etc/pki/tls/private"
I0112 18:14:21.281687       1 router.go:262] router "msg"="router is including routes in all namespaces"  
E0112 18:14:21.314274       1 reflector.go:138] pkg/router/controller/factory/factory.go:125: Failed to watch *v1.Route: failed to list *v1.Route: the server is currently unable to handle the request (get routes.route.openshift.io)
E0112 18:14:22.808063       1 reflector.go:138] pkg/router/controller/factory/factory.go:125: Failed to watch *v1.Route: failed to list *v1.Route: the server is currently unable to handle the request (get routes.route.openshift.io)
E0112 18:14:24.978721       1 reflector.go:138] pkg/router/controller/factory/factory.go:125: Failed to watch *v1.Route: failed to list *v1.Route: the server is currently unable to handle the request (get routes.route.openshift.io)
E0112 18:14:29.838509       1 reflector.go:138] pkg/router/controller/factory/factory.go:125: Failed to watch *v1.Route: failed to list *v1.Route: the server is currently unable to handle the request (get routes.route.openshift.io)
E0112 18:14:37.916451       1 reflector.go:138] pkg/router/controller/factory/factory.go:125: Failed to watch *v1.Route: failed to list *v1.Route: the server is currently unable to handle the request (get routes.route.openshift.io)
E0112 18:15:03.664444       1 reflector.go:138] pkg/router/controller/factory/factory.go:125: Failed to watch *v1.Route: failed to list *v1.Route: the server is currently unable to handle the request (get routes.route.openshift.io)
E0112 18:15:48.193689       1 reflector.go:138] pkg/router/controller/factory/factory.go:125: Failed to watch *v1.Route: failed to list *v1.Route: the server is currently unable to handle the request (get routes.route.openshift.io)

Existing workaround

setting NO_PROXY variables in /etc/environment with the external IP address of the board.