This message was deleted.
# terraform-provider-rancher2
a
This message was deleted.
a
For who cares, this is not possible as of yet to automate: https://docs.microsoft.com/en-us/azure/aks/private-clusters#hub-and-spoke-with-custom-dns In scenarios where the VNet containing your cluster has custom DNS settings (4), cluster deployment fails unless the private DNS zone is linked to the VNet that contains the custom DNS resolvers (5). This link can be created manually after the private zone is created during cluster provisioning or via automation upon detection of creation of the zone using event-based deployment mechanisms (for example, Azure Event Grid and Azure Functions).
­čś× 1
I wanted to add to this for clarifications sake, that it can be automated, as you can read in the last sentence, but just not with the Rancher2 module.