azure-docs
azure-docs copied to clipboard
Custom DNS name additional format
Custom DNS can have an additional format: private.westeurope.azmk8s.io
, which is not specified in documentation. According to the message:
It should be a valid resource id and the private dns zone name should be in either of these formats: 'private.westeurope.azmk8s.io,privatelink.westeurope.azmk8s.io,[a-zA-Z0-9-]{1,32}.private.westeurope.azmk8s.io,[a-zA-Z0-9-]{1,32}.privatelink.westeurope.azmk8s.io
In documentation only one format is specified:
CUSTOM_PRIVATE_DNS_ZONE_RESOURCE_ID", which requires you to create a Private DNS Zone in this format for Azure global cloud: privatelink.<region>.azmk8s.io or <subzone>.privatelink.<region>.azmk8s.io
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
- ID: 0b68f2c4-bb6c-11a2-6c61-8af4057a2438
- Version Independent ID: e3498bed-1447-6841-8353-9f1b5d3dc8df
- Content: Create a private Azure Kubernetes Service cluster - Azure Kubernetes Service
- Content Source: articles/aks/private-clusters.md
- Service: container-service
- GitHub Login: @MGoedtel
- Microsoft Alias: magoedte
@michalgozdowski Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.
@MGoedtel Can you please check and add your comments on this doc update request as applicable.
@VikasPullagura-MSFT - Yes, reviewing and investigating now to confirm.
@VikasPullagura-MSFT and @michalgozdowski - I'm opening a work item to update the article to fix this section of the article to be clearer about custom DNS format details, and confirm related details with the PG.
@michalgozdowski - I've been able to get clarification regarding the point you made about custom DNS name. There are two types of private cluster, private link based, which is what the article is based on (that is, version 1 of private cluster), and VNet injection using the API, which is private cluster version 2 (As described in this doc - https://learn.microsoft.com/en-us/azure/aks/api-server-vnet-integration).
The options correspond to the respective private cluster option being used.
I'll be updating the v1 article shortly to reflect those changes so it's clear.
I've opened an PR and it merged a short while ago that clarifies the details for using custom DNS between using private link or API Server VNet Integration. The articles go live later today. #please-close