Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ingress operator canary health checks failure #5677

Open
returntrip opened this issue Feb 20, 2025 · 0 comments
Open

Ingress operator canary health checks failure #5677

returntrip opened this issue Feb 20, 2025 · 0 comments

Comments

@returntrip
Copy link

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant