Service detail page: Show loadbalancer ip or hostname from the service status #6246
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.
Summary
Service detail page: Show loadbalancer ip or hostname from the service status, if the spec field is empty
Fixes #6245
Occurred changes and/or fixed issues
Currently the external IP is only shown, if it was defined in the Service spec. In most cases the external IP or hostname of a LoadBalancer Service is automatically assigned by the cloud provider though. In that case
spec.loadBalancerIP
is empty. But you can see the assigned information instatus.loadBalancer.ingress
.This PR shows the information from the status if the spec field is empty.
Technical notes summary
A lot of cloud providers assign a IP address to a load balancer service (e.g. AKS), but some assign a hostname (e.g. EKS).
Areas or cases that should be tested
Service detail page for services of type LoadBalancer, e.g. in an AKS, EKS or GKE cluster.
Areas which could experience regressions
Service detail page.
Screenshot/Video
Example on AKS
Example on EKS