Platform Center
Home / Platform management / Networking / Subnets / Create a subnet (Kube-OVN overlay network)

Create a subnet (Kube-OVN overlay network)

Create a subnet in Kube-OVN overlay network to achieve finer network isolation of resources in the cluster.

Tip: A join subnet is preconfigured in the platform for communication between nodes and container groups. Please avoid IP address conflicts between the join subnet and newly created subnets.

IP assignment rules

Create the subnets and assign namespaces

  1. In the left navigation bar, click Networking > Subnets.

  2. Click Create Subnet.

  3. Configure the relevant parameters according to the following instructions.

    Parameter Description
    Subnet After assigning the subnet to the namespace, the IP addresses in this subnet will be randomly assigned to the container groups.
    Reserved IP Addresses The reserved IP addresses will not be automatically assigned. For example, they can be used as the IP address of the Static IP Address of the computing component.
    Gateway Type Select the gateway type for the subnet to control the outbound traffic.
    - Distributed: Each host in the cluster can act as an outbound node for the container group on the current host, achieving distributed outbound traffic.
    - Centralized: All container groups in the cluster use one or more specific hosts as outbound nodes, making it easier for external auditing and firewall control. Setting up multiple centralized Gateway Nodes can achieve active-active protection.
    ECMP (Alpha) When selecting the Centralized gateway, you can use the ECMP (Equal-Cost Multipath Routing) feature. By default, the gateway operates in primary-backup mode, with only the primary gateway handling traffic. When ECMP is enabled, outbound traffic will be routed through multiple equivalent paths to all available gateway nodes, thereby increasing the overall gateway throughput.

    Note: Please enable ECMP-related features in advance.
    Outbound NAT Select whether to enable outbound traffic NAT (Network Address Translation), which is enabled by default.
    It is mainly used to set the exposed access address when the container group in the subnet accesses the external network.
    After enabling outbound traffic NAT, the host IP will be used as the access address for the container group in the current subnet. If it is not enabled, the IP addresses of the container groups in the subnet will be directly exposed to the external network. In this case, it is recommended to use a centralized gateway.

  4. Click Confirm.

  5. On the subnet details page, select Actions > Update Namespace.

  6. Complete the configuration and click Update.

Frequently Asked Questions

How to resolve cross-node communication issues in ARM environments?

When using lower kernel versions and certain domestic network cards, there may be errors in checksum calculation (Checksum) by the network card after enabling Checksum Offload, leading to communication failures between nodes in the Kube-OVN Overlay network. The specific solutions are as follows: