Hello all I m deploying flyte to aws eks I followed the inst

Question

Hello all I m deploying flyte to aws eks I followed the instructions in and everything seems to be set up However the ALB ingress controller is not giving me an address ``` $ kubectl n flyte get ingress NAME CLASS HOSTS ADDRESS PORTS AGE flyte core lt none gt 80 41m flyte core grpc lt none gt 80 41m``` This issue was mentioned in the troubleshooting section of the docs and it suggested running ```$ kubectl describe ingress n flyte Name flyte core Labels Namespace flyte Address Ingress Class lt none gt Default backend lt default gt Rules Host Path Backends ssl redirect use annotation lt error endpoints ssl redirect not found gt Annotations Type redirect RedirectConfig Protocol HTTPS Port 443 StatusCode HTTP 301 arn aws acm us east 1 752578504353 certificate 7a7065cb 1ffc 418e 8070 bc36fbaff7cb flyte HTTP 80 HTTPS 443 internet facing service instance=production alb flyte flyte console Events Type Reason Age From Message Warning FailedDeployModel 3m33s x20 over 42m ingress Failed deploy model due to InvalidParameter 1 validation error s found minimum field value of 1 CreateTargetGroupInput Port Name flyte core grpc Labels Namespace flyte Address Ingress Class lt none gt Default backend lt default gt Rules Host Path Backends Annotations Type redirect RedirectConfig Protocol HTTPS Port 443 StatusCode HTTP 301 Events Type Reason Age From Message Warning FailedDeployModel 3m36s x19 over 42m ingress Failed deploy model due to InvalidParameter 1 validation error s found minimum field value of 1 CreateTargetGroupInput Port ``` Could someone point me to the right direction in debugging this I checked the security groups of EKS cluster and RDS they were the same Thanks in advance Best Ekku CTO amp Co Founder

Shivay Lamba · Answer

Hi Ekku thanks for sharing your issue Can you check if the target group binding for the ALB is correctly configured once

Ekku Jokinen · Answer

Hey thanks for the follow up slightly smiling face I will check this first thing tomorrow

Ekku Jokinen · Answer

Hey < Shivay Lamba> sorry for the delay It seems like the ALB wasn t created which would explain the issue I suppose smile Although I m not sure why I believe I followed the steps and everything seemed fine

Shivay Lamba · Answer

Okay could you try to check through the steps and setup the ALB Let us know if you face any issues

Ekku Jokinen · Answer

I tried to run through the steps again still no address showing up on `kubectl n flyte get ingress` < Shivay Lamba> can you specify a bit more on how would I check the target group binding

Shivay Lamba · Answer

Hi Ekku let me get back to you

Laura Lin · Answer

When I saw this I had to add `<http alb ingress kubernetes io target type|alb ingress kubernetes io target type> ip ` to the ingress in values eks yaml

Ekku Jokinen · Answer

For sure < Shivay Lamba>

Ekku Jokinen · Answer

< Laura Lin> Thanks for the tip I actually saw someone else had suggested that in < CP2HDHKE1|ask the community> I tried that didn t work immediately though Did you have to adjust some other configurations for this I saw that AWS Load Balancer Controller docs say that ```IP mode Ingress traffic starts at the ALB and reaches the Kubernetes pods directly CNIs must support directly accessible POD ip via secondary IP addresses on ENI ``` was the ENI configured correctly for this automatically

Laura Lin · Answer

No once I added that setting to the ingress and upgraded the helm I was able to see it

Ekku Jokinen · Answer

Hmm okay I ll have to keep looking Thanks