Network configuration

Steps to configure the Red Hat® OpenShift® network and storage network. Use the defaults as is and customize only for any special CIDRs network requirements.

About this task

The OpenShift network page shows the OpenShift network to setup OpenShift and the storage configuration for the internal storage network of IBM Storage Fusion. You can use the default values in this page and customize values only whenever you have specific network requirements. The OpenShift network section allows you to override the default network CIDRs, which might collide with the data center networks. Also, it provides the flexibility to choose your own range during network planning.

Procedure

  1. In the Network settings wizard page, select Yes or No based on whether you plan to use Global Data Platform to enable Metro-DR.
  2. For Metro-DR setup, select whether it is the First cluster or Second cluster.
    During the Metro-DR stretch cluster installation on a secondary site, enable ping on ports 1191 and 12345. For more information about ports that must be enabled with pings, see IBM Storage Scale port usage.
  3. In the OpenShift network section, enter the following network configuration for Red Hat OpenShift.
    Important:
    • 100.64.0.0/16 is reserved for v4InternalSubnet by OVN and must not be used for CIDR in OpenShift Container Platform installation.
    • Use unique network values for Metro-DR clusters. The following values are pre-populated with unique values. If you want to change these values, ensure that the network setting used between the two Metro-DR sites are not duplicated.
    1. Enter Pod network CIDR. It is the IP address pools from which pod IP addresses are allocated. The default value is 10.128.0.0/14.
      Note: The Pod network CIDR must be different between site 1 and site 2 of Metro-DR.
    2. Enter Service network CIDR. It is the IP address pool for the services. The default value is 172.30.0.0/16.
      Note: The Service network CIDR must be different between site 1 and site 2 of Metro-DR.
    3. Enter Pod network Host Prefix. It is the subnet prefix length to assign to each individual node.

      For example, if hostPrefix is set to 23, then each node is assigned a /23 subnet out of the given CIDR. A hostPrefix value of 23 provides 510 (2^(32 - 23) - 2) pod IP addresses. The default value is 23.

  4. In the Storage network section, enter the following network configuration details for the internal storage network:
    Note: The CIDR address, Gateway address, and IP address range must be unique across site 1 and site 2.
    1. Enter CIDR address. It is the network subnet that is used for the multus additional storage network of the scale core pods. The default value is 192.168.128.0/18.
    2. Enter the Gateway address. It is the gateway address for the scale core Pods on the multus additional storage network that connects to the other site in a Metro-DR.
      Note: In Metro-DR, the gateway must be pre-configured in the customer data center.
    3. Enter the IP address range. It is the IP address pools from which scale core pod IP addresses are allocated for the multus additional storage network. The default range is 192.168.128.11 - 192.168.191.254.
    4. Click Next to go to the Custom certificate wizard page.