openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OSDOCS-17778 Document iDRAC10 support

Browse Source
This commit is contained in:
Ben Scott
2026-01-07 16:38:48 -05:00
committed by openshift-cherrypick-robot
parent 90ff424ff7
commit 02d24b2f29
2 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
installing/installing_bare_metal/ipi/ipi-install-overview.adoc
View File

@@ -6,7 +6,8 @@ include::_attributes/common-attributes.adoc[]
toc::[]
Installer-provisioned installation on bare metal nodes deploys and configures the infrastructure that an {product-title} cluster runs on. This guide provides a methodology to achieving a successful installer-provisioned bare-metal installation. The following diagram illustrates the installation environment in phase 1 of deployment:
[role="_abstract"]
Installer-provisioned installation on bare metal nodes deploys and configures the infrastructure that an {product-title} cluster runs on. By understanding the components of bare metal installation, you can prepare your infrastructure for a successful installation.
image::210_OpenShift_Baremetal_IPI_Deployment_updates_0122_1.png[Deployment phase one]
@@ -17,6 +18,12 @@ For the installation, the key elements in the previous diagram are:
- **Network bridges**: The bootstrap VM connects to the bare metal network and to the provisioning network, if present, via network bridges, `eno1` and `eno2`.
- **API VIP**: An API virtual IP address (VIP) is used to provide failover of the API server across the control plane nodes. The API VIP first resides on the bootstrap VM. A script generates the `keepalived.conf` configuration file before launching the service. The VIP moves to one of the control plane nodes after the bootstrap process has completed and the bootstrap VM stops.
[IMPORTANT]
====
The provisioning network is optional, but it is required for PXE booting. If you deploy without a provisioning network, you must use a virtual media baseboard management controller (BMC) addressing option such as `redfish-virtualmedia` or `idrac-virtualmedia`.
Installing a cluster using a provisioning network has not been tested and validated with Dell iDRAC 10. If you are installing a cluster with installer-provisioned infrastructure on iDRAC 10, it is recommended to use virtual media, which has been validated with iDRAC 10.
====
In phase 2 of the deployment, the provisioner destroys the bootstrap VM automatically and moves the virtual IP addresses (VIPs) to the appropriate nodes.
The `keepalived.conf` file sets the control plane machines with a lower Virtual Router Redundancy Protocol (VRRP) priority than the bootstrap VM, which ensures that the API on the control plane machines is fully functional before the API VIP moves from the bootstrap VM to the control plane. Once the API VIP moves to one of the control plane nodes, traffic sent from external clients to the API VIP routes to an `haproxy` load balancer running on that control plane node. This instance of `haproxy` load balances the API VIP traffic across the control plane nodes.
@@ -38,8 +45,3 @@ For installer-provisioned infrastructure installations, CoreDNS exposes port 53
.Additional resources
* xref:../../../networking/networking_operators/dns-operator.adoc#nw-dns-forward_dns-operator[Using DNS forwarding]
[IMPORTANT]
====
The provisioning network is optional, but it is required for PXE booting. If you deploy without a provisioning network, you must use a virtual media baseboard management controller (BMC) addressing option such as `redfish-virtualmedia` or `idrac-virtualmedia`.
====