VNet and subnets
When registering an Azure environment in Cloudera, you must select a VNet and one or more subnets.
-
Use your existing VNet and subnets for provisioning Cloudera resources.
-
Have Cloudera create a new VNet and subnets. All Cloudera resources will be provisioned into this new VNet and subnets.
Existing VNet and subnets
- The VNet has at least one subnet. If you are planning to run more than Cloudera Data Hub, you need additional subnets as specified in VNet and subnet planning.
- VNet can make an outbound connection to the Internet or set of CIDRs and ports provided by Cloudera.
- Configure service endpoints as described in Set up service endpoint for network. If you want to use private endpoints instead of service endpoints for Cloudera Data Hub, meet the requirements described in Private endpoint for PostgreSQL.
Verify the limits of the VNet and subnets available in your Azure subscription to ensure that you have enough resources to create clusters in Cloudera.
VNets can be created and managed from the . For detailed instructions on how to create a new VNet on Azure, see Create a virtual network using the Azure portal in the Azure documentation.
Egress connectivity for existing VNets and subnets
When you deploy an environment with an existing network of your own configuration, it is your responsibility to create egress connectivity for the required subnets in your VNet. Egress connectivity can be accomplished through a NAT gateway setup or user-defined routing. Alternatively, you can create a secondary load balancer for public egress. See Azure Load Balancers in Data Lake and Data Hub for more information.
