VNet and subnet planning

Because you are using your existing VNet for Cloudera, you should carefully plan your network, calculating and verifying the limits of the VNet and subnets available in your Azure subscription to ensure that you have enough networking resources to create clusters in Cloudera.

When registering an Azure environment in Cloudera, you must select a VNet and one or more subnets. Use this guide to calculate and verify the limits of the VNet and subnets available in your Azure subscription to ensure that you have enough networking resources to create clusters in Cloudera.

Existing VNet and subnets

When using your existing VNet, the subnet requirements vary based on the services used. The following is a guide to calculate network requirements per service.

Additionally, you must follow these guidelines:

You cannot use the following reserved CIDR blocks for your VNet:
- 10.0.0.0/16
- 10.244.0.0/16
- 172.17.0.1/16
- 10.20.0.0/16
- 10.244.0.0/16
The Microsoft.Storage and Microsoft.SQL Service endpoints should be registered for all subnets that will be used by Cloudera.

Subnets for Cloudera Data Hub

Only one subnet is required for Cloudera Data Hub.

Cloudera recommends a minimum of /24 CIDR. Follow these guidelines if you want to use a smaller subnet:

One IP address is used for each VM.
One Light Duty Data Lake cluster uses three VMs.
A typical Cloudera Data Hub cluster uses at least four VMs as a starting point, but this number can be dynamically scaled up or down.
Make sure you allocate enough IPs to handle each cluster running at peak capacity.