Cloudera Docs

Activating an Azure environment from Cloudera Data Warehouse

To use an Azure environment for Cloudera Data Warehouse on cloud you must first activate it.

When you activate an environment, Cloudera creates an AKS (Azure Kubernetes Services) cluster to host Kubernetes-based resources. The underlying compute, network resources are managed by Azure, including the following ones:
  • Resource group
  • Load balancer(s)
  • Public IP address(es)
  • Network security group
  • Disk(s)
Three instances are added to the cluster as needed for shared services (always on components). Three shared nodes are dStandard_E2s_v3 MemoryOptimized using flexserver, for the Amazon Relational Database Service (RDS). These shared nodes are used for Data Explorer and Data Visualization user metadata. For more information, see Always active, shared services.

Deploying a private AKS

If you want to deploy a Private AKS cluster, you must use the CDP CLI as described in AKS deployment configuration options.

  1. In the Cloudera Data Warehouse service, in Environments, locate the environment that you want to activate.
  2. Click Activate.
  3. In the Activate Environment page, under the Azure Configuration section, configure the following:
    • Select a Subnet inside the virtual network (VNet) that you want to use for Cloudera Data Warehouse.

      The VNet that you select must have a sufficient number of free IP addresses.

    • Select Enable internal load balancer (ingress) to distribute traffic inside a virtual network.

      For information about load balancers, see "Azure load balancers".

    • Specify a user-assigned, managed identity for the AKS cluster.
    • Optionally, select Enable availability zones for AKS.
    • Select Enable AKS monitoring and then select the workspace from the adjacent drop-down list.
  4. (Optional) In the Network Settings section, configure the following:
    • In the List of allowed IP-CIDR for the Kubernetes cluster, add trusted endpoint IP CIDRs for the Kubernetes cluster in a comma-separated list.
    • In the List of allowed IP-CIDR for the load balancer, add trusted endpoint IP CIDRs for your load balancer in a comma-separated list.
  5. In the Advanced Settings section, accept the default Use CNI overlay networking if IP address exhaustion is a concern for your deployment.
  6. Click ACTIVATE.