I'm porting an application to Azure that was orignally developed for Amazon's Fargate facility. A feature of Fargate is being able to create a private DNS zone and have the service names that it creates automatically register with this zone. This allows any Fargate service, as well as other VMs in the same VPC/subnet, to be able to reference the services by name using service-name.zone-name.
This is particularly useful for the VMs we have running in our product since they can make REST calls to the microservices running in Fargate directly by their automatically generated private DNS names.
We're using AKS in our Azure implementation and I've discovered that kubernetes provides a similar mechanism for the containers that it manages by creating records of the form service-name.namespace that map to the cluster IP of the services. This works fine within the kubernetes network but any VMs we have running in the same virtual network are unaware of these AKS service aliases.
So my question is this: Is there a way to make use of Azure's private DNS facility and tie it into AKS so that VMs that live in the same virtual network can also refer to the Kubernetes services by name rather than by IP address?
