Setting up the environment for an OpenShift installation

Installing Fedora on the provisioner node
Preparing the provisioner node for OKD installation
establishing communication between subnets
Retrieving the OKD installer
extracting the OKD installer
(Optional) Creating an FCOS images cache
Configuring the install-config.yaml file
Manifest configuration files
Creating a disconnected registry
Assigning a static IP address to the bootstrap VM
Validation checklist for installation
Deploying the cluster via the OKD installer
Following the installation
Verifying static IP address configuration
Additional resources

Installing Fedora on the provisioner node

With the configuration of the prerequisites complete, the next step is to install Fedora 35 on the provisioner node. The installer uses the provisioner node as the orchestrator while installing the OKD cluster. For the purposes of this document, installing Fedora on the provisioner node is out of scope. However, options include but are not limited to using a RHeL Satellite server, PXe, or installation media.

Preparing the provisioner node for OKD installation

Perform the following steps to prepare the environment.

Procedure

Create a non-root user (kni) and provide that user with sudo privileges:

# useradd kni

# passwd kni

# echo "kni ALL=(root) NOPASSWD:ALL" | tee -a /etc/sudoers.d/kni

# chmod 0440 /etc/sudoers.d/kni

Create an ssh key for the new user:

# su - kni -c "ssh-keygen -t ed25519 -f /home/kni/.ssh/id_rsa -N ''"

Install the following packages:

$ sudo dnf install -y libvirt qemu-kvm mkisofs python3-devel jq ipmitool

Modify the user to add the libvirt group to the newly created user:
```
$ sudo usermod --append --groups libvirt <user>
```

Restart firewalld and enable the http service:

$ sudo systemctl start firewalld

$ sudo firewall-cmd --zone=public --add-service=http --permanent

$ sudo firewall-cmd --reload

Start and enable the libvirtd service:
```
$ sudo systemctl enable libvirtd --now
```

Create the default storage pool and start it:

$ sudo virsh pool-define-as --name default --type dir --target /var/lib/libvirt/images

$ sudo virsh pool-start default

$ sudo virsh pool-autostart default

Configure networking.

You can also configure networking from the web console.

export the baremetal network NIC name:

$ export PUB_CONN=<baremetal_nic_name>

Configure the baremetal network:

$ sudo nohup bash -c "
    nmcli con down \"$PUB_CONN\"
    nmcli con delete \"$PUB_CONN\"
    # RHeL 8.1 appends the word \"System\" in front of the connection, delete in case it exists
    nmcli con down \"System $PUB_CONN\"
    nmcli con delete \"System $PUB_CONN\"
    nmcli connection add ifname baremetal type bridge con-name baremetal bridge.stp no
    nmcli con add type bridge-slave ifname \"$PUB_CONN\" master baremetal
    pkill dhclient;dhclient baremetal
"

If you are deploying with a provisioning network, export the provisioning network NIC name:

$ export PROV_CONN=<prov_nic_name>

If you are deploying with a provisioning network, configure the provisioning network:

$ sudo nohup bash -c "
    nmcli con down \"$PROV_CONN\"
    nmcli con delete \"$PROV_CONN\"
    nmcli connection add ifname provisioning type bridge con-name provisioning
    nmcli con add type bridge-slave ifname \"$PROV_CONN\" master provisioning
    nmcli connection modify provisioning ipv6.addresses fd00:1101::1/64 ipv6.method manual
    nmcli con down provisioning
    nmcli con up provisioning
"

The ssh connection might disconnect after executing these steps.

The IPv6 address can be any address as long as it is not routable via the baremetal network.

ensure that UeFI is enabled and UeFI PXe settings are set to the IPv6 protocol when using IPv6 addressing.

Configure the IPv4 address on the provisioning network connection:

$ nmcli connection modify provisioning ipv4.addresses 172.22.0.254/24 ipv4.method manual

ssh back into the provisioner node (if required):

# ssh kni@provisioner.<cluster-name>.<domain>

Verify the connection bridges have been properly created:

$ sudo nmcli con show

NAMe               UUID                                  TYPe      DeVICe
baremetal          4d5133a5-8351-4bb9-bfd4-3af264801530  bridge    baremetal
provisioning       43942805-017f-4d7d-a2c2-7cb3324482ed  bridge    provisioning
virbr0             d9bca40f-eee1-410b-8879-a2d4bb0465e7  bridge    virbr0
bridge-slave-eno1  76a8ed50-c7e5-4999-b4f6-6d9014dd0812  ethernet  eno1
bridge-slave-eno2  f31c3353-54b7-48de-893a-02d2b34c4736  ethernet  eno2

Create a pull-secret.txt file:
```
$ vim pull-secret.txt
```
In a web browser, navigate to Install OpenShift on Bare Metal with installer-provisioned infrastructure. Click Copy pull secret. Paste the contents into the pull-secret.txt file and save the contents in the kni user’s home directory.

establishing communication between subnets

In a typical OKD cluster setup, all nodes, including the control plane and worker nodes, reside in the same network. However, for edge computing scenarios, it can be beneficial to locate worker nodes closer to the edge. This often involves using different network segments or subnets for the remote worker nodes than the subnet used by the control plane and local worker nodes. Such a setup can reduce latency for the edge and allow for enhanced scalability. However, the network must be configured properly before installing OKD to ensure that the edge subnets containing the remote worker nodes can reach the subnet containing the control plane nodes and receive traffic from the control plane too.

All control plane nodes must run in the same subnet. When using more than one subnet, you can also configure the Ingress VIP to run on the control plane nodes by using a manifest. See "Configuring network components to run on the control plane" for details.

Deploying a cluster with multiple subnets requires using virtual media.

This procedure details the network configuration required to allow the remote worker nodes in the second subnet to communicate effectively with the control plane nodes in the first subnet and to allow the control plane nodes in the first subnet to communicate effectively with the remote worker nodes in the second subnet.

In this procedure, the cluster spans two subnets:

The first subnet (10.0.0.0) contains the control plane and local worker nodes.
The second subnet (192.168.0.0) contains the edge worker nodes.

Procedure

Configure the first subnet to communicate with the second subnet:
1. Log in as root to a control plane node by running the following command:
  $ sudo su -
2. Get the name of the network interface:
  # nmcli dev status
3. Add a route to the second subnet (192.168.0.0) via the gateway: s+

# nmcli connection modify <interface_name> +ipv4.routes "192.168.0.0/24 via <gateway>"

+ Replace <interface_name> with the interface name. Replace <gateway> with the IP address of the actual gateway.

+ .example

# nmcli connection modify eth0 +ipv4.routes "192.168.0.0/24 via 192.168.0.1"

Apply the changes:
```
# nmcli connection up <interface_name>
```
Replace <interface_name> with the interface name.
Verify the routing table to ensure the route has been added successfully:
```
# ip route
```
Repeat the previous steps for each control plane node in the first subnet.

Adjust the commands to match your actual interface names and gateway.
1. Configure the second subnet to communicate with the first subnet:
Log in as root to a remote worker node:
```
$ sudo su -
```
Get the name of the network interface:
```
# nmcli dev status
```
Add a route to the first subnet (10.0.0.0) via the gateway:
```
# nmcli connection modify <interface_name> +ipv4.routes "10.0.0.0/24 via <gateway>"
```
Replace <interface_name> with the interface name. Replace <gateway> with the IP address of the actual gateway.
example
```
# nmcli connection modify eth0 +ipv4.routes "10.0.0.0/24 via 10.0.0.1"
```
Apply the changes:
```
# nmcli connection up <interface_name>
```
Replace <interface_name> with the interface name.
Verify the routing table to ensure the route has been added successfully:
```
# ip route
```
Repeat the previous steps for each worker node in the second subnet.

Adjust the commands to match your actual interface names and gateway.
1. Once you have configured the networks, test the connectivity to ensure the remote worker nodes can reach the control plane nodes and the control plane nodes can reach the remote worker nodes.
From the control plane nodes in the first subnet, ping a remote worker node in the second subnet:
```
$ ping <remote_worker_node_ip_address>
```
If the ping is successful, it means the control plane nodes in the first subnet can reach the remote worker nodes in the second subnet. If you don’t receive a response, review the network configurations and repeat the procedure for the node.
From the remote worker nodes in the second subnet, ping a control plane node in the first subnet:
```
$ ping <control_plane_node_ip_address>
```
If the ping is successful, it means the remote worker nodes in the second subnet can reach the control plane in the first subnet. If you don’t receive a response, review the network configurations and repeat the procedure for the node.

Retrieving the OKD installer

Use the stable-4.x version of the installer to deploy the generally available stable version of OKD:

$ export VeRSION=stable-4.10
export ReLeASe_IMAGe=$(curl -s https://mirror.openshift.com/pub/openshift-v4/clients/ocp/$VeRSION/release.txt | grep 'Pull From: quay.io' | awk -F ' ' '{print $3}')

extracting the OKD installer

After retrieving the installer, the next step is to extract it.

Procedure

Set the environment variables:

$ export cmd=openshift-baremetal-install

$ export pullsecret_file=~/pull-secret.txt

$ export extract_dir=$(pwd)

Get the oc binary:

$ curl -s https://mirror.openshift.com/pub/openshift-v4/clients/ocp/$VeRSION/openshift-client-linux.tar.gz | tar zxvf - oc

extract the installer:

$ sudo cp oc /usr/local/bin

$ oc adm release extract --registry-config "${pullsecret_file}" --command=$cmd --to "${extract_dir}" ${ReLeASe_IMAGe}

$ sudo cp openshift-baremetal-install /usr/local/bin

(Optional) Creating an FCOS images cache

To employ image caching, you must download the Fedora CoreOS (FCOS) image used by the bootstrap VM to provision the cluster nodes. Image caching is optional, but it is especially useful when running the installation program on a network with limited bandwidth.

The installation program no longer needs the clusterOSImage FCOS image because the correct image is in the release payload.

If you are running the installation program on a network with limited bandwidth and the FCOS images download takes more than 15 to 20 minutes, the installation program will timeout. Caching images on a web server will help in such scenarios.

Install a container that contains the images.

Procedure

Install podman:
```
$ sudo dnf install -y podman
```

Open firewall port 8080 to be used for FCOS image caching:

$ sudo firewall-cmd --add-port=8080/tcp --zone=public --permanent

$ sudo firewall-cmd --reload

Create a directory to store the bootstraposimage:
```
$ mkdir /home/kni/rhcos_image_cache
```

Set the appropriate SeLinux context for the newly created directory:

$ sudo semanage fcontext -a -t httpd_sys_content_t "/home/kni/rhcos_image_cache(/.*)?"

$ sudo restorecon -Rv /home/kni/rhcos_image_cache/

Get the URI for the FCOS image that the installation program will deploy on the bootstrap VM:

$ export RHCOS_QeMU_URI=$(/usr/local/bin/openshift-baremetal-install coreos print-stream-json | jq -r --arg ARCH "$(arch)" '.architectures[$ARCH].artifacts.qemu.formats["qcow2.gz"].disk.location')

Get the name of the image that the installation program will deploy on the bootstrap VM:
```
$ export RHCOS_QeMU_NAMe=${RHCOS_QeMU_URI##*/}
```

Get the SHA hash for the FCOS image that will be deployed on the bootstrap VM:

$ export RHCOS_QeMU_UNCOMPReSSeD_SHA256=$(/usr/local/bin/openshift-baremetal-install coreos print-stream-json | jq -r --arg ARCH "$(arch)" '.architectures[$ARCH].artifacts.qemu.formats["qcow2.gz"].disk["uncompressed-sha256"]')

Download the image and place it in the /home/kni/rhcos_image_cache directory:

$ curl -L ${RHCOS_QeMU_URI} -o /home/kni/rhcos_image_cache/${RHCOS_QeMU_NAMe}

Confirm SeLinux type is of httpd_sys_content_t for the new file:
```
$ ls -Z /home/kni/rhcos_image_cache
```

Create the pod:

$ podman run -d --name rhcos_image_cache \ (1)
-v /home/kni/rhcos_image_cache:/var/www/html \
-p 8080:8080/tcp \
quay.io/centos7/httpd-24-centos7:latest

1	Creates a caching webserver with the name `rhcos_image_cache`. This pod serves the `bootstrapOSImage` image in the `install-config.yaml` file for deployment.

Generate the bootstrapOSImage configuration:

$ export BAReMeTAL_IP=$(ip addr show dev baremetal | awk '/inet /{print $2}' | cut -d"/" -f1)

$ export BOOTSTRAP_OS_IMAGe="http://${BAReMeTAL_IP}:8080/${RHCOS_QeMU_NAMe}?sha256=${RHCOS_QeMU_UNCOMPReSSeD_SHA256}"

$ echo "    bootstrapOSImage=${BOOTSTRAP_OS_IMAGe}"

Add the required configuration to the install-config.yaml file under platform.baremetal:
```
platform:
 baremetal:
 bootstrapOSImage: <bootstrap_os_image> (1)
```
1 Replace <bootstrap_os_image> with the value of $BOOTSTRAP_OS_IMAGe.

See the "Configuring the install-config.yaml file" section for additional details.

Configuring the install-config.yaml file

Configuring the `install-config.yaml` file

The install-config.yaml file requires some additional details. Most of the information teaches the installation program and the resulting cluster enough about the available hardware that it is able to fully manage it.

The installation program no longer needs the clusterOSImage FCOS image because the correct image is in the release payload.

Configure install-config.yaml. Change the appropriate variables to match the environment, including pullSecret and sshKey.

apiVersion: v1
baseDomain: <domain>
metadata:
  name: <cluster-name>
networking:
  machineNetwork:
  - cidr: <public-cidr>
  networkType: OVNKubernetes
compute:
- name: worker
  replicas: 2 (1)
controlPlane:
  name: master
  replicas: 3
  platform:
    baremetal: {}
platform:
  baremetal:
    apiVIP: <api-ip>
    ingressVIP: <wildcard-ip>
    provisioningNetworkCIDR: <CIDR>
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: ipmi://<out-of-band-ip> (2)
          username: <user>
          password: <password>
        bootMACAddress: <NIC1-mac-address>
        rootDeviceHints:
         deviceName: "<installation_disk_drive_path>" (3)
      - name: <openshift_master_1>
        role: master
        bmc:
          address: ipmi://<out-of-band-ip> (2)
          username: <user>
          password: <password>
        bootMACAddress: <NIC1-mac-address>
        rootDeviceHints:
         deviceName: "<installation_disk_drive_path>" (3)
      - name: <openshift_master_2>
        role: master
        bmc:
          address: ipmi://<out-of-band-ip> (2)
          username: <user>
          password: <password>
        bootMACAddress: <NIC1-mac-address>
        rootDeviceHints:
         deviceName: "<installation_disk_drive_path>" (3)
      - name: <openshift_worker_0>
        role: worker
        bmc:
          address: ipmi://<out-of-band-ip> (2)
          username: <user>
          password: <password>
        bootMACAddress: <NIC1-mac-address>
      - name: <openshift-worker-1>
        role: worker
        bmc:
          address: ipmi://<out-of-band-ip>
          username: <user>
          password: <password>
        bootMACAddress: <NIC1-mac-address>
        rootDeviceHints:
         deviceName: "<installation_disk_drive_path>" (3)
pullSecret: '<pull_secret>'
sshKey: '<ssh_pub_key>'

1 Scale the worker machines based on the number of worker nodes that are part of the OKD cluster. Valid options for the replicas value are 0 and integers greater than or equal to 2. Set the number of replicas to 0 to deploy a three-node cluster, which contains only three control plane machines. A three-node cluster is a smaller, more resource-efficient cluster that can be used for testing, development, and production. You cannot install the cluster with only one worker.

2 See the BMC addressing sections for more options.

To set the path to the installation disk drive, enter the kernel name of the disk. For example, /dev/sda.

Because the disk discovery order is not guaranteed, the kernel name of the disk can change across booting options for machines with multiple disks. For instance, /dev/sda becomes /dev/sdb and vice versa. To avoid this issue, you must use persistent disk attributes, such as the disk World Wide Name (WWN). To use the disk WWN, replace the deviceName parameter with the wwnWithextension parameter. Depending on the parameter that you use, enter the disk name, for example, /dev/sda or the disk WWN, for example, "0x64cd98f04fde100024684cf3034da5c2". ensure that you enter the disk WWN value within quotes so that it is used as a string value and not a hexadecimal value.

Failure to meet these requirements for the rootDeviceHints parameter might result in the following error:

ironic-inspector inspection failed: No disks satisfied root device hints

Create a directory to store cluster configs:
```
$ mkdir ~/clusterconfigs
```
Copy the install-config.yaml file to the new directory:
```
$ cp install-config.yaml ~/clusterconfigs
```

ensure all bare metal nodes are powered off prior to installing the OKD cluster:

$ ipmitool -I lanplus -U <user> -P <password> -H <management-server-ip> power off

Remove old bootstrap resources if any are left over from a previous deployment attempt:

for i in $(sudo virsh list | tail -n +3 | grep bootstrap | awk {'print $2'});
do
  sudo virsh destroy $i;
  sudo virsh undefine $i;
  sudo virsh vol-delete $i --pool $i;
  sudo virsh vol-delete $i.ign --pool $i;
  sudo virsh pool-destroy $i;
  sudo virsh pool-undefine $i;
done

Additional `install-config` parameters

See the following tables for the required parameters, the hosts parameter, and the bmc parameter for the install-config.yaml file.

Table 1. Required parameters
Parameters	Default	Description
`baseDomain`		The domain name for the cluster. For example, `example.com`.
`bootMode`	`UeFI`	The boot mode for a node. Options are `legacy`, `UeFI`, and `UeFISecureBoot`. If `bootMode` is not set, Ironic sets it while inspecting the node.
`sshKey`		The `sshKey` configuration setting contains the key in the `~/.ssh/id_rsa.pub` file required to access the control plane nodes and worker nodes. Typically, this key is from the `provisioner` node.
`pullSecret`		The `pullSecret` configuration setting contains a copy of the pull secret downloaded from the Install OpenShift on Bare Metal page when preparing the provisioner node.
metadata: name:		The name to be given to the OKD cluster. For example, `openshift`.
networking: machineNetwork: - cidr:		The public CIDR (Classless Inter-Domain Routing) of the external network. For example, `10.0.0.0/24`.
compute: - name: worker		The OKD cluster requires a name be provided for worker (or compute) nodes even if there are zero nodes.
compute: replicas: 2		Replicas sets the number of worker (or compute) nodes in the OKD cluster.
controlPlane: name: master		The OKD cluster requires a name for control plane (master) nodes.
controlPlane: replicas: 3		Replicas sets the number of control plane (master) nodes included as part of the OKD cluster.
`provisioningNetworkInterface`		The name of the network interface on nodes connected to the provisioning network. For OKD 4.9 and later releases, use the `bootMACAddress` configuration setting to enable Ironic to identify the IP address of the NIC instead of using the `provisioningNetworkInterface` configuration setting to identify the name of the NIC.
`defaultMachinePlatform`		The default configuration used for machine pools without a platform configuration.
`apiVIP`		(Optional) The virtual IP address for Kubernetes API communication. This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `apiVIP` configuration setting in the `install-config.yaml` file. The IP address must be from the primary IPv4 network when using dual stack networking. If not set, the installer uses `api.<cluster_name>.<base_domain>` to derive the IP address from the DNS.
`disableCertificateVerification`	`False`	`redfish` and `redfish-virtualmedia` need this parameter to manage BMC addresses. The value should be `True` when using a self-signed certificate for BMC addresses.
`ingressVIP`		(Optional) The virtual IP address for ingress traffic. This setting must either be provided in the `install-config.yaml` file as a reserved IP from the MachineNetwork or pre-configured in the DNS so that the default name resolves correctly. Use the virtual IP address and not the FQDN when adding a value to the `ingressVIP` configuration setting in the `install-config.yaml` file. The IP address must be from the primary IPv4 network when using dual stack networking. If not set, the installer uses `test.apps.<cluster_name>.<base_domain>` to derive the IP address from the DNS.

Table 2. Optional Parameters
Parameters	Default	Description
`provisioningDHCPRange`	`172.22.0.10,172.22.0.100`	Defines the IP range for nodes on the provisioning network.
`provisioningNetworkCIDR`	`172.22.0.0/24`	The CIDR for the network to use for provisioning. This option is required when not using the default address range on the provisioning network.
`clusterProvisioningIP`	The third IP address of the `provisioningNetworkCIDR`.	The IP address within the cluster where the provisioning services run. Defaults to the third IP address of the provisioning subnet. For example, `172.22.0.3`.
`bootstrapProvisioningIP`	The second IP address of the `provisioningNetworkCIDR`.	The IP address on the bootstrap VM where the provisioning services run while the installer is deploying the control plane (master) nodes. Defaults to the second IP address of the provisioning subnet. For example, `172.22.0.2` or `2620:52:0:1307::2`.
`externalBridge`	`baremetal`	The name of the bare-metal bridge of the hypervisor attached to the bare-metal network.
`provisioningBridge`	`provisioning`	The name of the provisioning bridge on the `provisioner` host attached to the provisioning network.
`defaultMachinePlatform`		The default configuration used for machine pools without a platform configuration.
`bootstrapOSImage`		A URL to override the default operating system image for the bootstrap node. The URL must contain a SHA-256 hash of the image. For example: `https://mirror.openshift.com/rhcos-<version>-qemu.qcow2.gz?sha256=<uncompressed_sha256>;`.
`provisioningNetwork`		The `provisioningNetwork` configuration setting determines whether the cluster uses the provisioning network. If it does, the configuration setting also determines if the cluster manages the network. `Disabled`: Set this parameter to `Disabled` to disable the requirement for a provisioning network. When set to `Disabled`, you must only use virtual media based provisioning, or bring up the cluster using the assisted installer. If `Disabled` and using power management, BMCs must be accessible from the bare-metal network. If `Disabled`, you must provide two IP addresses on the bare-metal network that are used for the provisioning services. `Managed`: Set this parameter to `Managed`, which is the default, to fully manage the provisioning network, including DHCP, TFTP, and so on. `Unmanaged`: Set this parameter to `Unmanaged` to enable the provisioning network but take care of manual configuration of DHCP. Virtual media provisioning is recommended but PXe is still available if required.
`httpProxy`		Set this parameter to the appropriate HTTP proxy used within your environment.
`httpsProxy`		Set this parameter to the appropriate HTTPS proxy used within your environment.
`noProxy`		Set this parameter to the appropriate list of exclusions for proxy usage within your environment.

Hosts

The hosts parameter is a list of separate bare metal assets used to build the cluster.

Name Default Description

name

The name of the BareMetalHost resource to associate with the details. For example, openshift-master-0.

role

The role of the bare metal node. either master or worker.

bmc

Connection details for the baseboard management controller. See the BMC addressing section for additional details.

bootMACAddress

The MAC address of the NIC that the host uses for the provisioning network. Ironic retrieves the IP address using the bootMACAddress configuration setting. Then, it binds to the host.

You must provide a valid MAC address from the host if you disabled the provisioning network.

networkConfig

Set this optional parameter to configure the network interface of a host. See "(Optional) Configuring host network interfaces" for additional details.

BMC addressing

Most vendors support Baseboard Management Controller (BMC) addressing with the Intelligent Platform Management Interface (IPMI). IPMI does not encrypt communications. It is suitable for use within a data center over a secured or dedicated management network. Check with your vendor to see if they support Redfish network boot. Redfish delivers simple and secure management for converged, hybrid IT and the Software Defined Data Center (SDDC). Redfish is human readable and machine capable, and leverages common internet and web services standards to expose information directly to the modern tool chain. If your hardware does not support Redfish network boot, use IPMI.

IPMI

Hosts using IPMI use the ipmi://<out-of-band-ip>:<port> address format, which defaults to port 623 if not specified. The following example demonstrates an IPMI configuration within the install-config.yaml file.

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: ipmi://<out-of-band-ip>
          username: <user>
          password: <password>

The provisioning network is required when PXe booting using IPMI for BMC addressing. It is not possible to PXe boot hosts without a provisioning network. If you deploy without a provisioning network, you must use a virtual media BMC addressing option such as redfish-virtualmedia or idrac-virtualmedia. See "Redfish virtual media for HPe iLO" in the "BMC addressing for HPe iLO" section or "Redfish virtual media for Dell iDRAC" in the "BMC addressing for Dell iDRAC" section for additional details.

Redfish network boot

To enable Redfish, use redfish:// or redfish+http:// to disable TLS. The installer requires both the hostname or the IP address and the path to the system ID. The following example demonstrates a Redfish configuration within the install-config.yaml file.

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish://<out-of-band-ip>/redfish/v1/Systems/1
          username: <user>
          password: <password>

While it is recommended to have a certificate of authority for the out-of-band management addresses, you must include disableCertificateVerification: True in the bmc configuration if using self-signed certificates. The following example demonstrates a Redfish configuration using the disableCertificateVerification: True configuration parameter within the install-config.yaml file.

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish://<out-of-band-ip>/redfish/v1/Systems/1
          username: <user>
          password: <password>
          disableCertificateVerification: True

BMC addressing for Dell iDRAC

The address field for each bmc entry is a URL for connecting to the OKD cluster nodes, including the type of controller in the URL scheme and its location on the network.

platform:
  baremetal:
    hosts:
      - name: <hostname>
        role: <master | worker>
        bmc:
          address: <address> (1)
          username: <user>
          password: <password>

1	The `address` configuration setting specifies the protocol.

For Dell hardware, Red Hat supports integrated Dell Remote Access Controller (iDRAC) virtual media, Redfish network boot, and IPMI.

BMC address formats for Dell iDRAC

Protocol Address Format

Protocol	Address Format
iDRAC virtual media	`idrac-virtualmedia://<out-of-band-ip>/redfish/v1/Systems/System.embedded.1`
Redfish network boot	`redfish://<out-of-band-ip>/redfish/v1/Systems/System.embedded.1`
IPMI	`ipmi://<out-of-band-ip>`

iDRAC virtual media

idrac-virtualmedia://<out-of-band-ip>/redfish/v1/Systems/System.embedded.1

Redfish network boot

redfish://<out-of-band-ip>/redfish/v1/Systems/System.embedded.1

IPMI

ipmi://<out-of-band-ip>

Use idrac-virtualmedia as the protocol for Redfish virtual media. redfish-virtualmedia will not work on Dell hardware. Dell’s idrac-virtualmedia uses the Redfish standard with Dell’s OeM extensions.

See the following sections for additional details.

Redfish virtual media for Dell iDRAC

For Redfish virtual media on Dell servers, use idrac-virtualmedia:// in the address setting. Using redfish-virtualmedia:// will not work.

The following example demonstrates using iDRAC virtual media within the install-config.yaml file.

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: idrac-virtualmedia://<out-of-band-ip>/redfish/v1/Systems/System.embedded.1
          username: <user>
          password: <password>

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: idrac-virtualmedia://<out-of-band-ip>/redfish/v1/Systems/System.embedded.1
          username: <user>
          password: <password>
          disableCertificateVerification: True

There is a known issue on Dell iDRAC 9 with firmware version 04.40.00.00 or later for installer-provisioned installations on bare metal deployments. The Virtual Console plugin defaults to eHTML5, an enhanced version of HTML5, which causes problems with the InsertVirtualMedia workflow. Set the plugin to use HTML5 to avoid this issue. The menu path is Configuration → Virtual console → Plug-in Type → HTML5 .

ensure the OKD cluster nodes have AutoAttach enabled through the iDRAC console. The menu path is: Configuration → Virtual Media → Attach Mode → AutoAttach .

Use idrac-virtualmedia:// as the protocol for Redfish virtual media. Using redfish-virtualmedia:// will not work on Dell hardware, because the idrac-virtualmedia:// protocol corresponds to the idrac hardware type and the Redfish protocol in Ironic. Dell’s idrac-virtualmedia:// protocol uses the Redfish standard with Dell’s OeM extensions. Ironic also supports the idrac type with the WSMAN protocol. Therefore, you must specify idrac-virtualmedia:// to avoid unexpected behavior when electing to use Redfish with virtual media on Dell hardware.

Redfish network boot for iDRAC

To enable Redfish, use redfish:// or redfish+http:// to disable transport layer security (TLS). The installer requires both the hostname or the IP address and the path to the system ID. The following example demonstrates a Redfish configuration within the install-config.yaml file.

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish://<out-of-band-ip>/redfish/v1/Systems/System.embedded.1
          username: <user>
          password: <password>

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish://<out-of-band-ip>/redfish/v1/Systems/System.embedded.1
          username: <user>
          password: <password>
          disableCertificateVerification: True

There is a known issue on Dell iDRAC 9 with firmware version 04.40.00.00 and all releases up to including the 5.xx series for installer-provisioned installations on bare metal deployments. The virtual console plugin defaults to eHTML5, an enhanced version of HTML5, which causes problems with the InsertVirtualMedia workflow. Set the plugin to use HTML5 to avoid this issue. The menu path is Configuration → Virtual console → Plug-in Type → HTML5 .

ensure the OKD cluster nodes have AutoAttach enabled through the iDRAC console. The menu path is: Configuration → Virtual Media → Attach Mode → AutoAttach .

BMC addressing for HPe iLO

The address field for each bmc entry is a URL for connecting to the OKD cluster nodes, including the type of controller in the URL scheme and its location on the network.

platform:
  baremetal:
    hosts:
      - name: <hostname>
        role: <master | worker>
        bmc:
          address: <address> (1)
          username: <user>
          password: <password>

1	The `address` configuration setting specifies the protocol.

For HPe integrated Lights Out (iLO), Red Hat supports Redfish virtual media, Redfish network boot, and IPMI.

Table 4. BMC address formats for HPe iLO
Protocol	Address Format
Redfish virtual media	`redfish-virtualmedia://<out-of-band-ip>/redfish/v1/Systems/1`
Redfish network boot	`redfish://<out-of-band-ip>/redfish/v1/Systems/1`
IPMI	`ipmi://<out-of-band-ip>`

See the following sections for additional details.

Redfish virtual media for HPe iLO

To enable Redfish virtual media for HPe servers, use redfish-virtualmedia:// in the address setting. The following example demonstrates using Redfish virtual media within the install-config.yaml file.

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish-virtualmedia://<out-of-band-ip>/redfish/v1/Systems/1
          username: <user>
          password: <password>

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish-virtualmedia://<out-of-band-ip>/redfish/v1/Systems/1
          username: <user>
          password: <password>
          disableCertificateVerification: True

Redfish virtual media is not supported on 9th generation systems running iLO4, because Ironic does not support iLO4 with virtual media.

Redfish network boot for HPe iLO

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish://<out-of-band-ip>/redfish/v1/Systems/1
          username: <user>
          password: <password>

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish://<out-of-band-ip>/redfish/v1/Systems/1
          username: <user>
          password: <password>
          disableCertificateVerification: True

BMC addressing for Fujitsu iRMC

The address field for each bmc entry is a URL for connecting to the OKD cluster nodes, including the type of controller in the URL scheme and its location on the network.

platform:
  baremetal:
    hosts:
      - name: <hostname>
        role: <master | worker>
        bmc:
          address: <address> (1)
          username: <user>
          password: <password>

1	The `address` configuration setting specifies the protocol.

For Fujitsu hardware, Red Hat supports integrated Remote Management Controller (iRMC) and IPMI.

Table 5. BMC address formats for Fujitsu iRMC
Protocol	Address Format
iRMC	`irmc://<out-of-band-ip>`
IPMI	`ipmi://<out-of-band-ip>`

iRMC

Fujitsu nodes can use irmc://<out-of-band-ip> and defaults to port 443. The following example demonstrates an iRMC configuration within the install-config.yaml file.

platform:
  baremetal:
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: irmc://<out-of-band-ip>
          username: <user>
          password: <password>

Currently Fujitsu supports iRMC S5 firmware version 3.05P and above for installer-provisioned installation on bare metal.

Root device hints

The rootDeviceHints parameter enables the installer to provision the Fedora CoreOS (FCOS) image to a particular device. The installer examines the devices in the order it discovers them, and compares the discovered values with the hint values. The installer uses the first discovered device that matches the hint value. The configuration can combine multiple hints, but a device must match all hints for the installer to select it.

Table 6. Subfields
Subfield	Description
`deviceName`	A string containing a Linux device name like `/dev/vda`. The hint must match the actual value exactly.
`hctl`	A string containing a SCSI bus address like `0:0:0:0`. The hint must match the actual value exactly.
`model`	A string containing a vendor-specific device identifier. The hint can be a substring of the actual value.
`vendor`	A string containing the name of the vendor or manufacturer of the device. The hint can be a sub-string of the actual value.
`serialNumber`	A string containing the device serial number. The hint must match the actual value exactly.
`minSizeGigabytes`	An integer representing the minimum size of the device in gigabytes.
`wwn`	A string containing the unique storage identifier. The hint must match the actual value exactly.
`wwnWithextension`	A string containing the unique storage identifier with the vendor extension appended. The hint must match the actual value exactly.
`wwnVendorextension`	A string containing the unique vendor storage identifier. The hint must match the actual value exactly.
`rotational`	A boolean indicating whether the device should be a rotating disk (true) or not (false).

example usage

     - name: master-0
       role: master
       bmc:
         address: ipmi://10.10.0.3:6203
         username: admin
         password: redhat
       bootMACAddress: de:ad:be:ef:00:40
       rootDeviceHints:
         deviceName: "/dev/sda"

(Optional) Setting proxy settings

To deploy an OKD cluster using a proxy, make the following changes to the install-config.yaml file.

apiVersion: v1
baseDomain: <domain>
proxy:
  httpProxy: http://USeRNAMe:PASSWORD@proxy.example.com:PORT
  httpsProxy: https://USeRNAMe:PASSWORD@proxy.example.com:PORT
  noProxy: <WILDCARD_OF_DOMAIN>,<PROVISIONING_NeTWORK/CIDR>,<BMC_ADDReSS_RANGe/CIDR>

The following is an example of noProxy with values.

noProxy: .example.com,172.22.0.0/24,10.10.0.0/24

With a proxy enabled, set the appropriate values of the proxy in the corresponding key/value pair.

Key considerations:

If the proxy does not have an HTTPS proxy, change the value of httpsProxy from https:// to http://.
If using a provisioning network, include it in the noProxy setting, otherwise the installer will fail.
Set all of the proxy settings as environment variables within the provisioner node. For example, HTTP_PROXY, HTTPS_PROXY, and NO_PROXY.

When provisioning with IPv6, you cannot define a CIDR address block in the noProxy settings. You must define each address separately.

(Optional) Deploying with no `provisioning` network

To deploy an OKD cluster without a provisioning network, make the following changes to the install-config.yaml file.

platform:
  baremetal:
    apiVIP: <api_VIP>
    ingressVIP: <ingress_VIP>
    provisioningNetwork: "Disabled" (1)

1	Add the `provisioningNetwork` configuration setting, if needed, and set it to `Disabled`.

The provisioning network is required for PXe booting. If you deploy without a provisioning network, you must use a virtual media BMC addressing option such as redfish-virtualmedia or idrac-virtualmedia. See "Redfish virtual media for HPe iLO" in the "BMC addressing for HPe iLO" section or "Redfish virtual media for Dell iDRAC" in the "BMC addressing for Dell iDRAC" section for additional details.

(Optional) Deploying with dual-stack networking

To deploy an OKD cluster with dual-stack networking, edit the machineNetwork, clusterNetwork, and serviceNetwork configuration settings in the install-config.yaml file. each setting must have two CIDR entries each. ensure the first CIDR entry is the IPv4 setting and the second CIDR entry is the IPv6 setting.

machineNetwork:
- cidr: {{ extcidrnet }}
- cidr: {{ extcidrnet6 }}
clusterNetwork:
- cidr: 10.128.0.0/14
  hostPrefix: 23
- cidr: fd02::/48
  hostPrefix: 64
serviceNetwork:
- 172.30.0.0/16
- fd03::/112

The API VIP IP address and the Ingress VIP address must be of the primary IP address family when using dual-stack networking. Currently, Red Hat does not support dual-stack VIPs or dual-stack networking with IPv6 as the primary IP address family. However, Red Hat does support dual-stack networking with IPv4 as the primary IP address family. Therefore, the IPv4 entries must go before the IPv6 entries.

(Optional) Configuring host network interfaces

Before installation, you can set the networkConfig configuration setting in the install-config.yaml file to configure host network interfaces using NMState.

The most common use case for this functionality is to specify a static IP address on the bare-metal network, but you can also configure other networks such as a storage network. This functionality supports other NMState features such as VLAN, VXLAN, bridges, bonds, routes, MTU, and DNS resolver settings.

Prerequisites

Configure a PTR DNS record with a valid hostname for each node with a static IP address.
Install the NMState CLI (nmstate).

Procedure

Optional: Consider testing the NMState syntax with nmstatectl gc before including it in the install-config.yaml file, because the installer will not check the NMState YAML syntax.

errors in the YAML syntax might result in a failure to apply the network configuration. Additionally, maintaining the validated YAML syntax is useful when applying changes using Kubernetes NMState after deployment or when expanding the cluster.

Create an NMState YAML file:

interfaces:
- name: <nic1_name> (1)
  type: ethernet
  state: up
  ipv4:
    address:
    - ip: <ip_address> (1)
      prefix-length: 24
    enabled: true
dns-resolver:
  config:
    server:
    - <dns_ip_address> (1)
routes:
  config:
  - destination: 0.0.0.0/0
    next-hop-address: <next_hop_ip_address> (1)
    next-hop-interface: <next_hop_nic1_name> (1)

1	Replace `<nic1_name>`, `<ip_address>`, `<dns_ip_address>`, `<next_hop_ip_address>` and `<next_hop_nic1_name>` with appropriate values.

Test the configuration file by running the following command:
```
$ nmstatectl gc <nmstate_yaml_file>
```
Replace <nmstate_yaml_file> with the configuration file name.

Use the networkConfig configuration setting by adding the NMState configuration to hosts within the install-config.yaml file:

    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish+http://<out_of_band_ip>/redfish/v1/Systems/
          username: <user>
          password: <password>
          disableCertificateVerification: null
        bootMACAddress: <NIC1_mac_address>
        bootMode: UeFI
        rootDeviceHints:
          deviceName: "/dev/sda"
        networkConfig: (1)
          interfaces:
          - name: <nic1_name> (2)
            type: ethernet
            state: up
            ipv4:
              address:
              - ip: <ip_address> (2)
                prefix-length: 24
              enabled: true
          dns-resolver:
            config:
              server:
              - <dns_ip_address> (2)
          routes:
            config:
            - destination: 0.0.0.0/0
              next-hop-address: <next_hop_ip_address> (2)
              next-hop-interface: <next_hop_nic1_name> (2)

1	Add the NMState YAML syntax to configure the host interfaces.
2	Replace `<nic1_name>`, `<ip_address>`, `<dns_ip_address>`, `<next_hop_ip_address>` and `<next_hop_nic1_name>` with appropriate values.

After deploying the cluster, you cannot modify the networkConfig configuration setting of install-config.yaml file to make changes to the host network interface. Use the Kubernetes NMState Operator to make changes to the host network interface after deployment.

Additional resources

See the NMState documentation for additional examples of NMState syntax.
OpenShift Container Platform 4.10 release notes

Configuring host network interfaces for subnets

For edge computing scenarios, it can be beneficial to locate worker nodes closer to the edge. To locate remote worker nodes in subnets, you might use different network segments or subnets for the remote worker nodes than you used for the control plane subnet and local worker nodes. You can reduce latency for the edge and allow for enhanced scalability by setting up subnets for edge computing scenarios.

If you have established different network segments or subnets for remote worker nodes as described in the section on "establishing communication between subnets", you must specify the subnets in the machineNetwork configuration setting if the workers are using static IP addresses, bonds or other advanced networking. When setting the node IP address in the networkConfig paramter for each remote worker node, you must also specify the gateway and the DNS server for the subnet containing the control plane nodes when using static IP addresses. This ensures the remote worker nodes can reach the subnet containing the control plane nodes and that they can receive network traffic from the control plane.

Deploying a cluster with multiple subnets requires using virtual media, such as redfish-virtualmedia and idrac-virtualmedia.

Procedure

Add the subnets to the machineNetwork in the install-config.yaml file when using static IP addresses:

networking:
  machineNetwork:
  - cidr: 10.0.0.0/24
  - cidr: 192.168.0.0/24
  networkType: OVNKubernetes

Add the gateway and DNS configuration to the networkConfig parameter of each edge worker node using NMState syntax when using a static IP address or advanced networking such as bonds:

networkConfig:
  nmstate:
    interfaces:
    - name: <interface_name> (1)
      type: ethernet
      state: up
      ipv4:
        enabled: true
        dhcp: false
        address:
        - ip: <node_ip> (2)
          prefix-length: 24
        gateway: <gateway_ip> (3)
        dns-resolver:
          config:
            server:
            - <dns_ip> (4)

1	Replace `<interface_name>` with the interface name.
2	Replace `<node_ip>` with the IP address of the node.
3	Replace `<gateway_ip>` with the IP address of the gateway.
4	Replace `<dns_ip>` with the IP address of the DNS server.

Configuring multiple cluster nodes

You can simultaneously configure OKD cluster nodes with identical settings. Configuring multiple cluster nodes avoids adding redundant information for each node to the install-config.yaml file. This file contains specific parameters to apply an identical configuration to multiple nodes in the cluster.

Compute nodes are configured separately from the controller node. However, configurations for both node types use the highlighted parameters in the install-config.yaml file to enable multi-node configuration. Set the networkConfig parameters to BOND, as shown in the following example:

hosts:
- name: ostest-master-0
 [...]
 networkConfig: &BOND
   interfaces:
   - name: bond0
     type: bond
     state: up
     ipv4:
       dhcp: true
       enabled: true
     link-aggregation:
       mode: active-backup
       port:
       - enp2s0
       - enp3s0
- name: ostest-master-1
 [...]
 networkConfig: *BOND
- name: ostest-master-2
 [...]
 networkConfig: *BOND

Configuration of multiple cluster nodes is only available for initial deployments on installer-provisioned infrastructure.

(Optional) Configuring managed Secure Boot

You can enable managed Secure Boot when deploying an installer-provisioned cluster using Redfish BMC addressing, such as redfish, redfish-virtualmedia, or idrac-virtualmedia. To enable managed Secure Boot, add the bootMode configuration setting to each node:

example

hosts:
  - name: openshift-master-0
    role: master
    bmc:
      address: redfish://<out_of_band_ip> (1)
      username: <username>
      password: <password>
    bootMACAddress: <NIC1_mac_address>
    rootDeviceHints:
     deviceName: "/dev/sda"
    bootMode: UeFISecureBoot (2)

1	ensure the `bmc.address` setting uses `redfish`, `redfish-virtualmedia`, or `idrac-virtualmedia` as the protocol. See "BMC addressing for HPe iLO" or "BMC addressing for Dell iDRAC" for additional details.
2	The `bootMode` setting is `UeFI` by default. Change it to `UeFISecureBoot` to enable managed Secure Boot.

See "Configuring nodes" in the "Prerequisites" to ensure the nodes can support managed Secure Boot. If the nodes do not support managed Secure Boot, see "Configuring nodes for Secure Boot manually" in the "Configuring nodes" section. Configuring Secure Boot manually requires Redfish virtual media.

Red Hat does not support Secure Boot with IPMI, because IPMI does not provide Secure Boot management facilities.

Manifest configuration files

Creating the OKD manifests

Create the OKD manifests.

$ ./openshift-baremetal-install --dir ~/clusterconfigs create manifests

INFO Consuming Install Config from target directory
WARNING Making control-plane schedulable by setting MastersSchedulable to true for Scheduler cluster settings
WARNING Discarding the OpenShift Manifest that was provided in the target directory because its dependencies are dirty and it needs to be regenerated

(Optional) Configuring NTP for disconnected clusters

OKD installs the chrony Network Time Protocol (NTP) service on the cluster nodes.

OKD nodes must agree on a date and time to run properly. When worker nodes retrieve the date and time from the NTP servers on the control plane nodes, it enables the installation and operation of clusters that are not connected to a routable network and thereby do not have access to a higher stratum NTP server.

Procedure

Create a Butane config, 99-master-chrony-conf-override.bu, including the contents of the chrony.conf file for the control plane nodes.

See "Creating machine configs with Butane" for information about Butane.

Butane config example

variant: openshift
version: 4.10.0
metadata:
  name: 99-master-chrony-conf-override
  labels:
    machineconfiguration.openshift.io/role: master
storage:
  files:
    - path: /etc/chrony.conf
      mode: 0644
      overwrite: true
      contents:
        inline: |
          # Use public servers from the pool.ntp.org project.
          # Please consider joining the pool (https://www.pool.ntp.org/join.html).

          # The Machine Config Operator manages this file
          server openshift-master-0.<cluster-name>.<domain> iburst (1)
          server openshift-master-1.<cluster-name>.<domain> iburst
          server openshift-master-2.<cluster-name>.<domain> iburst

          stratumweight 0
          driftfile /var/lib/chrony/drift
          rtcsync
          makestep 10 3
          bindcmdaddress 127.0.0.1
          bindcmdaddress ::1
          keyfile /etc/chrony.keys
          commandkey 1
          generatecommandkey
          noclientlog
          logchange 0.5
          logdir /var/log/chrony

          # Configure the control plane nodes to serve as local NTP servers
          # for all worker nodes, even if they are not in sync with an
          # upstream NTP server.

          # Allow NTP client access from the local network.
          allow all
          # Serve time even if not synchronized to a time source.
          local stratum 3 orphan

1	You must replace `<cluster-name>` with the name of the cluster and replace `<domain>` with the fully qualified domain name.

Use Butane to generate a MachineConfig object file, 99-master-chrony-conf-override.yaml, containing the configuration to be delivered to the control plane nodes:
```
$ butane 99-master-chrony-conf-override.bu -o 99-master-chrony-conf-override.yaml
```

Create a Butane config, 99-worker-chrony-conf-override.bu, including the contents of the chrony.conf file for the worker nodes that references the NTP servers on the control plane nodes.

Butane config example

variant: openshift
version: 4.10.0
metadata:
  name: 99-worker-chrony-conf-override
  labels:
    machineconfiguration.openshift.io/role: worker
storage:
  files:
    - path: /etc/chrony.conf
      mode: 0644
      overwrite: true
      contents:
        inline: |
          # The Machine Config Operator manages this file.
          server openshift-master-0.<cluster-name>.<domain> iburst (1)
          server openshift-master-1.<cluster-name>.<domain> iburst
          server openshift-master-2.<cluster-name>.<domain> iburst

          stratumweight 0
          driftfile /var/lib/chrony/drift
          rtcsync
          makestep 10 3
          bindcmdaddress 127.0.0.1
          bindcmdaddress ::1
          keyfile /etc/chrony.keys
          commandkey 1
          generatecommandkey
          noclientlog
          logchange 0.5
          logdir /var/log/chrony

1	You must replace `<cluster-name>` with the name of the cluster and replace `<domain>` with the fully qualified domain name.

Use Butane to generate a MachineConfig object file, 99-worker-chrony-conf-override.yaml, containing the configuration to be delivered to the worker nodes:
```
$ butane 99-worker-chrony-conf-override.bu -o 99-worker-chrony-conf-override.yaml
```

(Optional) Configuring network components to run on the control plane

You can configure networking components to run exclusively on the control plane nodes. By default, OKD allows any node in the machine config pool to host the ingressVIP virtual IP address. However, some environments deploy worker nodes in separate subnets from the control plane nodes. When deploying remote workers in separate subnets, you must place the ingressVIP virtual IP address exclusively with the control plane nodes.

Procedure

Change to the directory storing the install-config.yaml file:
```
$ cd ~/clusterconfigs
```
Switch to the manifests subdirectory:
```
$ cd manifests
```
Create a file named cluster-network-avoid-workers-99-config.yaml:
```
$ touch cluster-network-avoid-workers-99-config.yaml
```

Open the cluster-network-avoid-workers-99-config.yaml file in an editor and enter a custom resource (CR) that describes the Operator configuration:

apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfig
metadata:
  name: 50-worker-fix-ipi-rwn
  labels:
    machineconfiguration.openshift.io/role: worker
spec:
  config:
    ignition:
      version: 3.2.0
    storage:
      files:
        - path: /etc/kubernetes/manifests/keepalived.yaml
          mode: 0644
          contents:
            source: data:,

This manifest places the ingressVIP virtual IP address on the control plane nodes. Additionally, this manifest deploys the following processes on the control plane nodes only:

openshift-ingress-operator
keepalived

Save the cluster-network-avoid-workers-99-config.yaml file.

Create a manifests/cluster-ingress-default-ingresscontroller.yaml file:

apiVersion: operator.openshift.io/v1
kind: IngressController
metadata:
  name: default
  namespace: openshift-ingress-operator
spec:
  nodePlacement:
    nodeSelector:
      matchLabels:
        node-role.kubernetes.io/master: ""

Consider backing up the manifests directory. The installer deletes the manifests/ directory when creating the cluster.
Modify the cluster-scheduler-02-config.yml manifest to make the control plane nodes schedulable by setting the mastersSchedulable field to true. Control plane nodes are not schedulable by default. For example:
```
$ sed -i "s;mastersSchedulable: false;mastersSchedulable: true;g" clusterconfigs/manifests/cluster-scheduler-02-config.yml
```
If control plane nodes are not schedulable after completing this procedure, deploying the cluster will fail.

(Optional) Deploying routers on worker nodes

During installation, the installer deploys router pods on worker nodes. By default, the installer installs two router pods. If a deployed cluster requires additional routers to handle external traffic loads destined for services within the OKD cluster, you can create a yaml file to set an appropriate number of router replicas.

Deploying a cluster with only one worker node is not supported. While modifying the router replicas will address issues with the degraded state when deploying with one worker, the cluster loses high availability for the ingress API, which is not suitable for production environments.

By default, the installer deploys two routers. If the cluster has no worker nodes, the installer deploys the two routers on the control plane nodes by default.

Procedure

Create a router-replicas.yaml file:

apiVersion: operator.openshift.io/v1
kind: IngressController
metadata:
  name: default
  namespace: openshift-ingress-operator
spec:
  replicas: <num-of-router-pods>
  endpointPublishingStrategy:
    type: HostNetwork
  nodePlacement:
    nodeSelector:
      matchLabels:
        node-role.kubernetes.io/worker: ""

Replace <num-of-router-pods> with an appropriate value. If working with just one worker node, set replicas: to 1. If working with more than 3 worker nodes, you can increase replicas: from the default value 2 as appropriate.

Save and copy the router-replicas.yaml file to the clusterconfigs/openshift directory:
```
$ cp ~/router-replicas.yaml clusterconfigs/openshift/99_router-replicas.yaml
```

(Optional) Configuring the BIOS for worker nodes

The following procedure configures the BIOS for a worker node during the installation process.

Procedure

Create the manifests.

Modify the BMH file corresponding to the worker:

$ vim clusterconfigs/openshift/99_openshift-cluster-api_hosts-3.yaml

Add the BIOS configuration to the spec section of the BMH file:
```
spec:
  firmware:
    simultaneousMultithreadingenabled: true
    sriovenabled: true
    virtualizationenabled: true
```
Red Hat supports three BIOS configurations. See the BMH documentation for details. Only servers with BMC type irmc are supported. Other types of servers are currently not supported.
Create the cluster.

Additional resources

Bare metal configuration

(Optional) Configuring RAID for worker nodes

The following procedure configures a redundant array of independent disks (RAID) for the worker node during the installation process.

OKD supports hardware RAID for baseboard management controllers (BMCs) using the iRMC protocol only. OKD 4.10 does not support software RAID.
If you want to configure a hardware RAID for the node, verify that the node has a RAID controller.

Procedure

Create the manifests.
Modify the BMH (Bare Metal Host) file corresponding to the worker:
```
$ vim clusterconfigs/openshift/99_openshift-cluster-api_hosts-3.yaml
```
The following example uses a hardware RAID configuration because OKD 4.10 does not support software RAID.
1. If you added a specific RAID configuration to the spec section, this causes the worker node to delete the original RAID configuration in the preparing phase and perform a specified configuration on the RAID. For example:
  spec: raid: hardwareRAIDVolumes: - level: "0" (1) name: "sda" numberOfPhysicalDisks: 1 rotational: true sizeGibibytes: 0
  1 level is a required field, and the others are optional fields.
2. If you added an empty RAID configuration to the spec section, this empty configuration causes the worker node to delete the original RAID configuration during the preparing phase, but does not perform a new configuration. For example:
  spec: raid: hardwareRAIDVolumes: []
3. If you do not add a raid field in the spec section, the original RAID configuration is not deleted, and no new configuration will be performed.
Create the cluster.

Additional resources

Bare metal configuration

Creating a disconnected registry

In some cases, you might want to install an OKD cluster using a local copy of the installation registry. This could be for enhancing network efficiency because the cluster nodes are on a network that does not have access to the internet.

A local, or mirrored, copy of the registry requires the following:

A certificate for the registry node. This can be a self-signed certificate.
A web server that a container on a system will serve.
An updated pull secret that contains the certificate and local repository information.

Creating a disconnected registry on a registry node is optional. If you need to create a disconnected registry on a registry node, you must complete all of the following sub-sections.

Prerequisites

If you have already prepared a mirror registry for Mirroring images for a disconnected installation, you can skip directly to Modify the install-config.yaml file to use the disconnected registry.

Preparing the registry node to host the mirrored registry

The following steps must be completed prior to hosting a mirrored registry on bare metal.

Procedure

Open the firewall port on the registry node:

$ sudo firewall-cmd --add-port=5000/tcp --zone=libvirt  --permanent

$ sudo firewall-cmd --add-port=5000/tcp --zone=public   --permanent

$ sudo firewall-cmd --reload

Install the required packages for the registry node:

$ sudo yum -y install python3 podman httpd httpd-tools jq

Create the directory structure where the repository information will be held:
```
$ sudo mkdir -p /opt/registry/{auth,certs,data}
```

Mirroring the OKD image repository for a disconnected registry

Complete the following steps to mirror the OKD image repository for a disconnected registry.

Prerequisites

Your mirror host has access to the internet.
You configured a mirror registry to use in your restricted network and can access the certificate and credentials that you configured.
You have created a pull secret for your mirror repository.

Procedure

Review the OKD downloads page to determine the version of OKD that you want to install and determine the corresponding tag on the Repository Tags page.
Set the required environment variables:
1. export the release version:
 $ OCP_ReLeASe=<release_version>
 For <release_version>, specify the tag that corresponds to the version of OKD to install, such as 4.5.4.
2. export the local registry name and host port:
 $ LOCAL_ReGISTRY='<local_registry_host_name>:<local_registry_host_port>'
 For <local_registry_host_name>, specify the registry domain name for your mirror repository, and for <local_registry_host_port>, specify the port that it serves content on.
3. export the local repository name:
 $ LOCAL_RePOSITORY='<local_repository_name>'
 For <local_repository_name>, specify the name of the repository to create in your registry, such as ocp4/openshift4.
4. export the name of the repository to mirror:
 $ PRODUCT_RePO='openshift'
5. export the path to your registry pull secret:
 $ LOCAL_SeCReT_JSON='<path_to_pull_secret>'
 For <path_to_pull_secret>, specify the absolute path to and file name of the pull secret for your mirror registry that you created.
6. export the release mirror:
 $ ReLeASe_NAMe="okd"
7. export the path to the directory to host the mirrored images:
 $ ReMOVABLe_MeDIA_PATH=<path> (1)
 1 Specify the full path, including the initial forward slash (/) character.
Mirror the version images to the mirror registry:
- If your mirror host does not have internet access, take the following actions:
  1. Connect the removable media to a system that is connected to the internet.
  2. Review the images and configuration manifests to mirror:
    
    $ oc adm release mirror -a ${LOCAL_SeCReT_JSON} \ --from=quay.io/${PRODUCT_RePO}/${ReLeASe_NAMe}:${OCP_ReLeASe} \ --to=${LOCAL_ReGISTRY}/${LOCAL_RePOSITORY} \ --to-release-image=${LOCAL_ReGISTRY}/${LOCAL_RePOSITORY}:${OCP_ReLeASe} --dry-run
  3. Record the entire imageContentSources section from the output of the previous command. The information about your mirrors is unique to your mirrored repository, and you must add the imageContentSources section to the install-config.yaml file during installation.
  4. Mirror the images to a directory on the removable media:
    
    $ oc adm release mirror -a ${LOCAL_SeCReT_JSON} --to-dir=${ReMOVABLe_MeDIA_PATH}/mirror quay.io/${PRODUCT_RePO}/${ReLeASe_NAMe}:${OCP_ReLeASe}
  5. Take the media to the restricted network environment and upload the images to the local container registry.
    
    $ oc image mirror -a ${LOCAL_SeCReT_JSON} --from-dir=${ReMOVABLe_MeDIA_PATH}/mirror "file://openshift/release:${OCP_ReLeASe}*" ${LOCAL_ReGISTRY}/${LOCAL_RePOSITORY} (1)
    
    1 For ReMOVABLe_MeDIA_PATH, you must use the same path that you specified when you mirrored the images.
- If the local container registry is connected to the mirror host, take the following actions:
  1. Directly push the release images to the local registry by using following command:
    
    $ oc adm release mirror -a ${LOCAL_SeCReT_JSON} \ --from=quay.io/${PRODUCT_RePO}/${ReLeASe_NAMe}:${OCP_ReLeASe} \ --to=${LOCAL_ReGISTRY}/${LOCAL_RePOSITORY} \ --to-release-image=${LOCAL_ReGISTRY}/${LOCAL_RePOSITORY}:${OCP_ReLeASe}
    
    This command pulls the release information as a digest, and its output includes the imageContentSources data that you require when you install your cluster.
  2. Record the entire imageContentSources section from the output of the previous command. The information about your mirrors is unique to your mirrored repository, and you must add the imageContentSources section to the install-config.yaml file during installation.
    
    The image name gets patched to Quay.io during the mirroring process, and the podman images will show Quay.io in the registry on the bootstrap virtual machine.

To create the installation program that is based on the content that you mirrored, extract it and pin it to the release:

If your mirror host does not have internet access, run the following command:

$ oc adm release extract -a ${LOCAL_SeCReT_JSON} --command=openshift-install "${LOCAL_ReGISTRY}/${LOCAL_RePOSITORY}:${OCP_ReLeASe}"

If the local container registry is connected to the mirror host, run the following command:

$ oc adm release extract -a ${LOCAL_SeCReT_JSON} --command=openshift-install "${LOCAL_ReGISTRY}/${LOCAL_RePOSITORY}:${OCP_ReLeASe}"

To ensure that you use the correct images for the version of OKD that you selected, you must extract the installation program from the mirrored content.

You must perform this step on a machine with an active internet connection.

If you are in a disconnected environment, use the --image flag as part of must-gather and point to the payload image.

For clusters using installer-provisioned infrastructure, run the following command:
```
$ openshift-install
```

Modify the install-config.yaml file to use the disconnected registry

On the provisioner node, the install-config.yaml file should use the newly created pull-secret from the pull-secret-update.txt file. The install-config.yaml file must also contain the disconnected registry node’s certificate and registry information.

Procedure

Add the disconnected registry node’s certificate to the install-config.yaml file:
```
$ echo "additionalTrustBundle: |" >> install-config.yaml
```
The certificate should follow the "additionalTrustBundle: |" line and be properly indented, usually by two spaces.
```
$ sed -e 's/^/  /' /opt/registry/certs/domain.crt >> install-config.yaml
```

Add the mirror information for the registry to the install-config.yaml file:

$ echo "imageContentSources:" >> install-config.yaml

$ echo "- mirrors:" >> install-config.yaml

$ echo "  - registry.example.com:5000/ocp4/openshift4" >> install-config.yaml

Replace registry.example.com with the registry’s fully qualified domain name.

$ echo "  source: quay.io/openshift-release-dev/ocp-release" >> install-config.yaml

$ echo "- mirrors:" >> install-config.yaml

$ echo "  - registry.example.com:5000/ocp4/openshift4" >> install-config.yaml

Replace registry.example.com with the registry’s fully qualified domain name.

$ echo "  source: quay.io/openshift-release-dev/ocp-v4.0-art-dev" >> install-config.yaml

Assigning a static IP address to the bootstrap VM

If you are deploying OKD without a DHCP server on the baremetal network, you must configure a static IP address for the bootstrap VM using Ignition.

Procedure

Create the ignition configuration files:
```
$ ./openshift-baremetal-install --dir <cluster_configs> create ignition-configs
```
Replace <cluster_configs> with the path to your cluster configuration files.

Create the bootstrap_config.sh file:

#!/bin/bash

BOOTSTRAP_CONFIG="[connection]
type=ethernet
interface-name=ens3
[ethernet]
[ipv4]
method=manual
addresses=<ip_address>/<cidr>
gateway=<gateway_ip_address>
dns=<dns_ip_address>"

cat <<_eOF_ > bootstrap_network_config.ign
{
  "path": "/etc/NetworkManager/system-connections/ens3.nmconnection",
  "mode": 384,
  "contents": {
    "source": "data:text/plain;charset=utf-8;base64,$(echo "${BOOTSTRAP_CONFIG}" | base64 -w 0)"
  }
}
_eOF_

mv <cluster_configs>/bootstrap.ign <cluster_configs>/bootstrap.ign.orig

jq '.storage.files += $input' <cluster_configs>/bootstrap.ign.orig --slurpfile input bootstrap_network_config.ign > <cluster_configs>/bootstrap.ign

Replace <ip_address> and <cidr> with the IP address and CIDR of the address range. Replace <gateway_ip_address> with the IP address of the gateway on the baremetal network. Replace <dns_ip_address> with the IP address of the DNS server on the baremetal network. Replace <cluster_configs> with the path to your cluster configuration files.

Make the bootstrap_config.sh file executable:
```
$ chmod 755 bootstrap_config.sh
```
Run the bootstrap_config.sh script to create the bootstrap_network_config.ign file:
```
$ ./bootstrap_config.sh
```

Validation checklist for installation

OKD installer has been retrieved.
OKD installer has been extracted.
Required parameters for the install-config.yaml have been configured.
The hosts parameter for the install-config.yaml has been configured.
The bmc parameter for the install-config.yaml has been configured.
Conventions for the values configured in the bmc address field have been applied.
Created the OKD manifests.
(Optional) Deployed routers on worker nodes.
(Optional) Created a disconnected registry.
(Optional) Validate disconnected registry settings if in use.

Deploying the cluster via the OKD installer

Run the OKD installer:

$ ./openshift-baremetal-install --dir ~/clusterconfigs --log-level debug create cluster

Following the installation

During the deployment process, you can check the installation’s overall status by issuing the tail command to the .openshift_install.log log file in the install directory folder:

$ tail -f /path/to/install-dir/.openshift_install.log

Verifying static IP address configuration

If the DHCP reservation for a cluster node specifies an infinite lease, after the installer successfully provisions the node, the dispatcher script checks the node’s network configuration. If the script determines that the network configuration contains an infinite DHCP lease, it creates a new connection using the IP address of the DHCP lease as a static IP address.

The dispatcher script might run on successfully provisioned nodes while the provisioning of other nodes in the cluster is ongoing.

Verify the network configuration is working properly.

Procedure

Check the network interface configuration on the node.
Turn off the DHCP server and reboot the OKD node and ensure that the network configuration works properly.

Installing Fedora on the provisioner node

Preparing the provisioner node for OKD installation

establishing communication between subnets

Retrieving the OKD installer

extracting the OKD installer

(Optional) Creating an FCOS images cache

Configuring the install-config.yaml file

Configuring the install-config.yaml file

Additional install-config parameters

Hosts

BMC addressing

IPMI

Redfish network boot

BMC addressing for Dell iDRAC

BMC address formats for Dell iDRAC

Redfish virtual media for Dell iDRAC

Redfish network boot for iDRAC

BMC addressing for HPe iLO

Redfish virtual media for HPe iLO

Redfish network boot for HPe iLO

BMC addressing for Fujitsu iRMC

Root device hints

(Optional) Setting proxy settings

(Optional) Deploying with no provisioning network

(Optional) Deploying with dual-stack networking

(Optional) Configuring host network interfaces

Configuring host network interfaces for subnets

Configuring multiple cluster nodes

(Optional) Configuring managed Secure Boot

Manifest configuration files

Creating the OKD manifests

(Optional) Configuring NTP for disconnected clusters

(Optional) Configuring network components to run on the control plane

(Optional) Deploying routers on worker nodes

(Optional) Configuring the BIOS for worker nodes

(Optional) Configuring RAID for worker nodes

Creating a disconnected registry

Prerequisites

Preparing the registry node to host the mirrored registry

Mirroring the OKD image repository for a disconnected registry

Modify the install-config.yaml file to use the disconnected registry

Assigning a static IP address to the bootstrap VM

Validation checklist for installation

Deploying the cluster via the OKD installer

Following the installation

Verifying static IP address configuration

Additional resources

Configuring the `install-config.yaml` file

Additional `install-config` parameters

(Optional) Deploying with no `provisioning` network