VNet and subnets
When registering an Azure environment in CDP, you will be asked to select a VNet and one or more subnets.
You have two options:
- Use your existing VNet and subnets for provisioning CDP resources.
- Have CDP create a new VNet and subnets. All CDP resources will be provisioned into this new VNet and subnets.
Existing VNet and subnets
If you would like to use your own VNet, it needs to fulfill the following requirements:
- The VNet has at least one subnet.
- VNet should be able to make an outbound connection with the internet or set of CIDRs and ports provided by Cloudera.
Verify the limits of the VNet and subnets available in your Azure subscription to ensure that you have enough resources to create clusters in CDP.
New VNet and subnets
If you would like CDP to create a new VNet, three subnets will be created automatically. You will need to specify a valid CIDR in IPv4 range that will be used to define the range of private IPs for VM instances provisioned into these subnets. Default is 10.10.0.0/16. Consider changing the IP range to correspond to corporate policies for standardized IP address ranges. You will need to divide the address space as follows:
- 32 x /24 private subnet for ML
- 3 x /19 private subnet for DW
- 3 x /19 private subnet for Data Lake and Data Hub
- 3 x /24 public subnet
For more information, refer to VNet and subnet planning.