Azure
Feature: Support Traffic Manager Profiles, Traffic Manager Endpoints and DNS CNAME record
Added support for Traffic Manager Profiles, Traffic Manager Endpoints and DNS zone CNAME records would be great. This way the service operator would be able to operate it's cluster in a "self sustained" load balanced environment (ie. failover clusters, load multi-region deployments and similar scenarios) and act as a replacement for the ExternalDNS component often used for single cluster installations.
As the traffic manager profiles obviously will be shared with other Kubernetes clusters (and/or other webserveres) this needs to be taken into consideration during provisioning. We could easily get a situation where multiple clusters (with their own operators) might try to create/update the same profile. The same applys to the DNS CNAME record which would point to a single traffic manager profile.
Each cluster should have it's own endpoint configuration - pointing to the ingress IP of choice. Being able to automatically fetch this from a reference to a namespace+ingress would be a huge time saver in terms of usability and generalization.
This issue has been automatically marked as stale because it has not had activity in 60 days.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
Microsoft.network/DnsZone and Microsoft.network/DnsZone/recordSets were added via #2918.
Azure public DNS is implemented but Traffic Manager profile is still in the backlog. Would be interested for it too
