![]() Ensure that the nodes are recent enough to support RHEL 8 for the provisioner node and RHCOS 8 for the control plane and worker nodes. Additionally, RHEL 8 ships with the most recent drivers for RAID controllers. Installer-provisioned installation relies on BMC protocols, which must be compatible across nodes. Latest generation: Nodes must be of the most recent generation. ![]() You may use IPMI, Redfish, or a proprietary protocol. That is, Red Hat recommends nodes be the same brand and model with the same CPU, memory and storage configuration.īaseboard Management Controller: The provisioner node must be able to access the baseboard management controller (BMC) of each OpenShift Container Platform cluster node. Similar nodes: Red Hat recommends nodes have an identical configuration per role. Deploying the provisioner node as a worker node using Metal3ĬPU architecture: All nodes must use x86_64 CPU architecture.Adding a worker node to an existing cluster Preparing the provisioner node to be deployed as a worker node Diagnosing a duplicate MAC address when provisioning a new host in the cluster.Preparing to deploy with Virtual Media on the baremetal network Enabling a provisioning network after installation Configuring NTP for disconnected clusters (optional) Installer-provisioned post-installation configuration Verifying static IP address configuration Deploying the cluster via the OpenShift Container Platform installer Modify the install-config.yaml file to use the disconnected registry (optional) Copy and update the pull-secret (optional) Creating the registry podman container (optional) Generating the self-signed certificate (optional) Preparing the registry node to host the mirrored registry (optional) ![]() Creating a disconnected registry (optional) Configure network components to run on the control plane Creating the OpenShift Container Platform manifests
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |