A CLM cluster must be configured with at least one virtual IP for client/ingress traffic, distinct from any cluster node IP addresses. This requirement for virtual IPs applies to CLM deployments with a single network interface, and to multi network interface deployments.

Each CLM cluster node that is an ingress gateway must have a network interface address that belongs to the same subnet for each VIP configured to the cluster.

The CLM supports IPv4 and IPv6 network connectivity in the CLM architecture.

The following limitations and restrictions apply to deploying the CLM with IPv6 network communications:

• The deployer host for a CLM cluster must have IPv4 connectivity to CLM cluster nodes. The CLM cluster can be configured for IPv6 communications for CLM applications, but must have IPv4 connectivity to the deployer node.

• Common web browser applications have security policies that may prevent the use of bracketed IPv6 addresses in the URL browser bar. Customers who use IPv6 networking for client communications to the CLM must use the hostname configuration.

• The CLM Kubernetes cluster communications uses internal addressing in 10.233.0.0/18 subnet. Customers should avoid using this subnet in their CLM deployment on VM network interfaces.

The CLM can be deployed with multiple network interfaces using IPv4 and IPv6 addressing.