search

cilium / cilium-service-mesh-beta

Instructions and issue tracking for Service Mesh capabilities of Cilium
Apache License 2.0
104 stars 14 forks source link

Kubernetes Ingress external IP address not populated on EKS #5

Open lizrice opened 2 years ago

lizrice commented 2 years ago

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.