Skip to content

assisted-installer-configuring-networking.adoc

Latest commit

 

History

History
51 lines (32 loc) · 2.61 KB

assisted-installer-configuring-networking.adoc

File metadata and controls

51 lines (32 loc) · 2.61 KB

Configuring networking

Before installing {product-title}, you must configure the cluster network.

Procedure

  1. In the Networking page, select one of the following if it is not already selected for you:

    • Cluster-Managed Networking: Selecting cluster-managed networking means that the {ai-full} will configure a standard network topology, including keepalived and Virtual Router Redundancy Protocol (VRRP) for managing the API and Ingress VIP addresses.

    • User-Managed Networking: Selecting user-managed networking allows you to deploy {product-title} with a non-standard network topology. For example, if you want to deploy with an external load balancer instead of keepalived and VRRP, or if you intend to deploy the cluster nodes across many distinct L2 network segments.

  2. For cluster-managed networking, configure the following settings:

    1. Define the Machine network. You can use the default network or select a subnet.

    2. Define an API virtual IP. An API virtual IP provides an endpoint for all users to interact with, and configure the platform.

    3. Define an Ingress virtual IP. An Ingress virtual IP provides an endpoint for application traffic flowing from outside the cluster.

  3. For user-managed networking, configure the following settings:

    1. Select your Networking stack type:

      • IPv4: Select this type when your hosts are only using IPv4.

      • Dual-stack: You can select dual-stack when your hosts are using IPv4 together with IPv6.

    2. Define the Machine network. You can use the default network or select a subnet.

    3. Define an API virtual IP. An API virtual IP provides an endpoint for all users to interact with, and configure the platform.

    4. Define an Ingress virtual IP. An Ingress virtual IP provides an endpoint for application traffic flowing from outside the cluster.

    5. Optional: You can select Allocate IPs via DHCP server to automatically allocate the API IP and Ingress IP using the DHCP server.

  4. Optional: Select Use advanced networking to configure the following advanced networking properties:

    • Cluster network CIDR: Define an IP address block from which Pod IP addresses are allocated.

    • Cluster network host prefix: Define a subnet prefix length to assign to each node.

    • Service network CIDR: Define an IP address to use for service IP addresses.

    • Network type: Select either Software-Defined Networking (SDN) for standard networking or Open Virtual Networking (OVN) for telco features.