Using Hostname if external IP is not found #505
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Openshift Service resource of LoadBalancer type might have EXTERNAL-IP in form of standartd static IP or in form of hostname
See
versus
This PR should allow the testsuite to work if EXTERNAL-IP is configured either way.
Verification Steps
Eye review. You can run a single test that uses keycloak against a cluster backed by Openstack (such clusters use static IP approach) and against another cluster backed by AWS (hostname approach).