Ingress operator canary health checks failure

[returntrip]

I am having an issue where the ingress-operator for the hosted cluster is unable to perform canary health checks. If I unset the HTTPS_PROXY within the ingress-operator pod then I can curl into the canary healthcheck endpoint.

I believe this PR should take care of this issue, but in my case it does not seem to work: #1131

bash-5.1$ curl -kI https://canary-openshift-ingress-canary.apps.wkldcl05.evilcorp.internal
HTTP/1.1 502 Bad Gateway
Content-Type: text/plain
Content-Length: 442
curl: (56) Received HTTP code 502 from proxy after CONNECT


bash-5.1$ unset HTTPS_PROXY
bash-5.1$ curl -kI https://canary-openshift-ingress-canary.apps.wkldcl05.evilcorp.internal
HTTP/2 200
x-request-port: 8443
content-type: text/plain; charset=utf-8
content-length: 22
date: Thu, 20 Feb 2025 15:25:38 GMT

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale