External IP Not Provisioning EKS

Question

I have an EKS cluster that is not assigning an External LB to the gateway. Ive seen many post about this but no solution has worked from what Ive found yet. See picture below:

enter image description here

Anyways, I've consulted a few friends that are Kubernetes Pros, and i've been told basically, that essentially the ingress pod has a listener port that does health checks on from istiod and i need to ensure that istiod is properly syncing with istio ingress and/or port forwarding.

![Enter image description here](/media/postImages/original/IMdNHvnSDFRIyxVxsrTDF6_A)

![Enter image description here](/media/postImages/original/IMDRFNgdd9ThKmo0dvbB3wdQ)

Given that the cluster seems to be configured correctly to assign the External LB, how can i best fix this port-forwarding/ istiod not communicating with the ingress to then achieve teh goal of, provisioning my External IP?

Im running on:

Mac M2
VSCode
Istio Gateway API
EKS (Used Terraform to Configure This)
AWS LB
Any help is MUCH appreciated! Thanks!

Ive tried everything from reinitiating the port forwarding and killing the processes in place, and it has not worked. Everytime we re-initiate port forwaridng we get this error on port 15000

Answer

Please check on below the confirguration items 
Examine AWS LB: Look at the AWS Load Balancer to see if it's been provisioned and is in a healthy state. Sometimes, the Load Balancer takes time to get provisioned or there could be issues with security groups or subnets preventing it from working correctly.

Debugging Port Forwarding and Istiod Communication
Port Forwarding Error: Regarding the error on port 15000, this is commonly used for Envoy's admin interface. Ensure that no other process is using this port. You might need to use lsof -i :15000 on your Mac to check the port

External IP Not Provisioning EKS

Relevant content