Making service names available externally
As we mentioned in the introduction, you may remember that we used IP addresses to test the LoadBalancer services we created, whereas for our Ingress examples, we used domain names. Why did we have to use IP addresses instead of a hostname for our LoadBalancer services?
Although a Kubernetes load balancer assigns a standard IP address to a service, it doesn’t automatically generate a DNS name for workloads to access the service. Instead, you must rely on IP addresses to connect to applications within the cluster, which becomes confusing and inefficient. Furthermore, manually registering DNS names for each IP assigned by MetalLB presents a maintenance challenge. To deliver a more cloud-like experience and streamline name resolution for LoadBalancer services, we need an add-on that can address these limitations.
Similar to the team that maintains KinD, there is a Kubernetes SIG that is working on this feature for Kubernetes called...
