Configuring an existing private DNS Zone for an AKS
At the Cloudera-level, when you provision the environment, you can configure an existing Azure Private DNS zone for an Azure Kubernetes Service (AKS). Alternatively, if you do not have an existing private DNS zone configured, the system can create a new private DNS zone for the AKS.
If all the following statements are true, the system uses the private DNS zone that
you specify in the aksPrivateDnsZoneId parameter while provisioning
the environment for the AKS:
- The private network is enabled (the
privateNetwork.enabledparameter is set totrue) - While provisioning the environment using CLI, the
aksPrivateDnsZoneIdparameter is configured - The
LIFTIE_AKS_DISABLE_PRIVATE_DNS_ZONEparameter is set to false (default)
If all the following statements are true, the system creates and enables a new private DNS zone for the AKS:
- The private network is enabled (the
privateNetwork.enabledparameter is set totrue) - The
aksPrivateDnsZoneIdparameter is not set - The
LIFTIE_AKS_DISABLE_PRIVATE_DNS_ZONEparameter is set to false (default)
To configure an existing Azure Private DNS zone for an AKS, you need the full resource ID of the private DNS zone. To obtain the full resource ID, use the JSON view option in . Example for the full resource ID of a private DNS zone for an AKS:
/subscriptions/[***SUBSCRIPTIONID***]/resourceGroups/[***RESOURCEGROUP***]/providers/Microsoft.Network/privateDnsZones/privatelink.[***REGION***].azmk8s.ioFor
information on how to create the environment for Cloudera Data Engineering, see Register an Azure environment from CDP CLI and
Obtain CLI commands for registering an
environment.