infra login and infra list report errors while Infra Engine load balancer DNS resolves

[jmorganca]

Since it may take a few minutes for the Infra Engine's load balancer to provision and resolve, it may be in a state where it does not resolve for a few minutes:

jmorgan@mba infra % infra list
❌

     NAME                      TYPE  STATUS                                                                                  
  *  infra:testing-118-public  k8s   💻 → 🌎 → ❌ Can't reach endpoint                                                       
                                      "ac94f6d7ca92344b8a82985c865bdffa-615121052.us-east-2.elb.amazonaws.com:8443"           
                                      (Get                                                                                    
                                      "https://ac94f6d7ca92344b8a82985c865bdffa-615121052.us-east-2.elb.amazonaws.com:8443":  
                                      dial tcp: lookup                                                                        
                                      ac94f6d7ca92344b8a82985c865bdffa-615121052.us-east-2.elb.amazonaws.com:                 
                                      no such host)     

We should add a health check on the Infra Engine side to examine it's own load balancer prior to registering itself it to the Infra Registry

[mxyng]

The port 8443 is odd here. Is that the port exposed by the LB?

[jmorganca]

Oops, that was just me testing a custom Infra Engine port, but this would happen regardless of the port