Networking

In this section, you will configure the networking for the Inforiver deployment.

• You can either use an existing virtual network (bring your own VNet) or create a new virtual network from this section.

• If you are using an existing virtual network, ensure that the required subnets have been created according to the deployment requirements. Select the existing virtual network from the drop-down list, and then choose the appropriate Private, Public, and Background subnets.

• If you choose to create a new virtual network, you can retain the default configuration and proceed to the next section.

• If you want to modify the default virtual network configuration, select Edit virtual network. In the pane that opens, update the address space and subnet configurations as required. Ensure that the Private, Public and Background subnets each have at least 32 IP addresses (/27) allocated. If the background processor is deployed on AKS, allocate at least 256 IP addresses (/24) for the Background subnet.

• Configure the AKS Service CIDR, which defines the cluster-internal Kubernetes service address range. The Service CIDR must not overlap with the virtual network (VNet) address space.

• Specify the AKS DNS Service IP. This IP address must belong to the configured AKS Service CIDR.

• Optional: To deploy a NAT gateway with a standard public IP attached to all subnets, select the Deploy NAT Gateway checkbox. This feature is not available for Bring Your Own VNet.

• Optional: To deploy the AKS cluster as a private cluster, select Make AKS Cluster Private.

You may also change the VNet and subnet names while you are in the edit network screen. The VNet name provided here would be concatenated with the solution name and used while creating the virtual network.

Networking details