[FEATURE] Allow to set the dns record for a private load balancer service via annotations

[guidola]

What happened: When exposing a service via a private Azure Load Balancer one is unable to define the dns record under which that service should be exposesd.

What you expected to happen: Ability to provide an annotation besides service.beta.kubernetes.io/azure-load-balancer-internal: "true" such as service.beta.kubernetes.io/azure-load-balancer-dns-record: "service.internal.domain.com" through which aks would register the dns entry as part of the service creation.

While this feature is not present one needs to have corresponding IaC code to create the dns records for each k8s service exposed via loadbalancer which breaks the independence of the k8s resources.

One would need to grant dns zone contributor rights to the AKS cluster identity for this work.

Anything else we need to know?:

Environment:

• Kubernetes version (use kubectl version): 1.20.7
• Size of cluster (how many worker nodes are in the cluster?) 10
• General description of workloads in the cluster (e.g. HTTP microservices, Java app, Ruby on Rails, machine learning, etc.) misc load
• Others:

[ghost]

Hi guidola, AKS bot here :wave: Thank you for posting on the AKS Repo, I'll do my best to get a kind human from the AKS team to assist you.

I might be just a bot, but I'm told my suggestions are normally quite good, as such: 1) If this case is urgent, please open a Support Request so that our 24/7 support team may help you faster. 2) Please abide by the AKS repo Guidelines and Code of Conduct. 3) If you're having an issue, could it be described on the AKS Troubleshooting guides or AKS Diagnostics? 4) Make sure your subscribed to the AKS Release Notes to keep up to date with all that's new on AKS. 5) Make sure there isn't a duplicate of this issue already reported. If there is, feel free to close this one and '+1' the existing issue. 6) If you have a question, do take a look at our AKS FAQ. We place the most common ones there!

[ghost]

Triage required from @Azure/aks-pm

[ghost]

Action required from @Azure/aks-pm

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads

[blacklabnz]

This is exactly what I would request too. Currently having to set it up manually. Please add this annotation, thanks

[guidola]

@blacklabnz You can use https://github.com/kubernetes-sigs/external-dns to have DNS auto set up for your ingresses and services. Although it would solve the need it seems to still make sense to have that annotation native as part of the AKS offering to avoid additional dependencies as with that you would need to deploy an additional controller.

[ghost]

Issue needing attention of @Azure/aks-leads

[ghost]

Issue needing attention of @Azure/aks-leads