When RKM runs as a Windows service, it can start before an IP address / DNS entry is available

This causes the Windows service to quickly fail with:

Category: Redpoint.KubernetesManager.Implementations.LocalEthernetInfo
EventId: 0

Unable to detect local IP address of machine!

Category: Redpoint.KubernetesManager.Implementations.WindowsNetworkingConfiguration
EventId: 0

Unable to locate network adapter name for IP address , which is necessary to set up networking on Windows.

The code that locates the IP address looks like this:

        private IPAddress? GetExternalIPAddress()
        {
            var myIPHostEntry = Dns.GetHostEntry(Dns.GetHostName());

            foreach (var myIPAddress in myIPHostEntry.AddressList)
            {
                if (myIPAddress.AddressFamily == System.Net.Sockets.AddressFamily.InterNetwork)
                {
                    if (!IsPrivateIP(myIPAddress))
                    {
                        _logger.LogInformation($"Detected local IP address as: {myIPAddress.ToString()}");
                        return myIPAddress;
                    }
                }
            }

            _logger.LogError($"Unable to detect local IP address of machine!");
            return null;
        }

We should make this code take into account when the machine was started, and if the machine was booted less than 10 minutes ago, continually retry up until that 10 minute threshold. That will give the DNS cache enough time to populate the machine's current external address.

If that isn't a reliable enough fix, we could also try parsing the route table to see what IP address outbound Internet connections are routed on, since that's what we actually want to be getting here.