-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Fix the router tests host name to use the external load balancer service #21799
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
Fix the router tests host name to use the external load balancer service #21799
Conversation
25a4198 to
ef1ea64
Compare
ef1ea64 to
d4f3359
Compare
host name if it is available. On aws when the proxy protocol is enabled, the cluster ip would talk the "proxy" protocol, so we have to use the external load balancer host name to talk http[s].
d4f3359 to
9dec900
Compare
|
@ironcladlou updated - I just simplified the change to let the initial value be what it originally was and set to a valid hostname if the type is load balancer (it also waits for a value to be populated in) and tests all passed - PTAL and approve - the PROXY protocol PR is blocked behind this. Thx |
|
Thanks! /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ironcladlou, ramr The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Flake: |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
host name if it is available.
On aws when the proxy protocol is enabled, the cluster ip would talk the
"proxy" protocol, so we have to use the external load balancer host name to
talk http[s].
This is blocking openshift/cluster-ingress-operator#84 tests.
@ironcladlou PTAL thx