Making service names available externally
You may have been wondering why we were using the IP addresses to test some of the services that we created, while we used domain names for our Ingress examples.
While a Kubernetes load balancer provides a standard IP address to a service, it does not create an external DNS name for users to connect to the service. Using IP addresses to connect to applications running on a cluster is not very efficient, and manually registering names in DNS for each IP assigned by MetalLB would be an impossible method to maintain. So how would you provide a more cloud-like experience to adding name resolution to our LoadBalancer services?
Similar to the team that maintains KinD, there is a Kubernetes SIG that is working on this feature to Kubernetes called ExternalDNS. The main project page can be found on the SIG's GitHub at https://github.com/kubernetes-sigs/external-dns.
At the time of writing, the ExternalDNS project supports a long list...
