You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2022. It is now read-only.
On EKS, the External IP field for a LoadBalancer service gets populated with a FQDN rather than an IP address. This isn't being populated into the Kubernetes Ingress.
❯ kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
cilium-ingress-basic-ingress LoadBalancer 10.100.156.98 a76b899eca0f842a080eb0fdaea5436b-594605697.eu-west-1.elb.amazonaws.com
❯ kubectl get ingress
Warning: extensions/v1beta1 Ingress is deprecated in v1.14+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
NAME CLASS HOSTS ADDRESS PORTS AGE
basic-ingress cilium * 80 9m57s
Connectivity is not affected, the external address works fine - it's just that you can't query it from the Ingress resource.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On EKS, the External IP field for a LoadBalancer service gets populated with a FQDN rather than an IP address. This isn't being populated into the Kubernetes Ingress.
Connectivity is not affected, the external address works fine - it's just that you can't query it from the Ingress resource.
The text was updated successfully, but these errors were encountered: