Custom Domain names or Zones with HTTP Application Routing Feature
While HTTP Application Routing feature brings a simple and managed ingress with domain management to AKS. Being able to define a custom domain name or a preexisting Azure Zone to be used with the HTTP Application Routing feature would bring more flexibility to the product.
Matteo Dell'Aquila commented
You can manage custom domains easily by manually installing external-dns as indicated here https://github.com/kubernetes-incubator/external-dns/blob/master/docs/tutorials/azure.md
You can also use helm for the setup https://github.com/helm/charts/tree/master/stable/external-dns
(NB "HTTP Application Routing" add-on is not recommended for production use.)
Sergei Ryabkov commented
I completely agree this is needed. HTTP Application Routing seems to rely on https://github.com/kubernetes-incubator/external-dns to create DNS entries, but it does not allow for custom domain names, even though the OSS version of external-dns does.
If the AKS team decides not to implement this feature, documentation should explain how to remove/disable/unbundle the AKS implementation of external-dns and replace it with the OSS version.
By the way, this request seems to be created in the wrong category (Azure Container Instances)
There doesn't seem to be a category for AKS on User Voice (feedback.azure.com)
Are AKS feature request supposed to be logged here (feedback.azure.com) or on GitHub? It looks like some AKS requests were moved from UserVoice to GitHub. See https://feedback.azure.com/forums/602224-azure-container-instances/suggestions/32855575-implement-rbac-authorization-for-kubernetes-in-aks for an example.