Skip to content
Step by step guide to deploy OCP4 UPI on baremetal without PXE and with static IPs
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs
.gitignore
LICENSE
README.md

README.md

Intro

The objective of this document is to provide instructions (automated ish) to install OCP4 on baremetal:

  • without PXE (pretty common scenario in big companies)
  • avoid installing stuff and use containers instead (instead yum/dnf install httpd, haproxy,... use containers)
  • use rootless containers if possible
  • use Fedora29/RHEL8 stuff (nmcli, firewalld, etc.)

DISCLAIMER: This is unofficial and unsupported procedure. Use the official OpenShift documentation for the supported scenarios.

Current status

OCP4.1 GA installed

Environment

In order to have a frictionless environment, a helper node will be used to achieve the OpenShift prerrequisites, including DNS entries, a load balancer and a httpd server to host some files required for the installation. If your enviorment has already a DNS server, load balancer and/or httpd server, you can use those instead.

Usage Hostname IP NOTES
Helper ocp4-helper.minwi.lan 192.168.32.2 DNS, httpd & load balancer
Bootstrap ocp4-bootstrap.minwi.lan 192.168.32.99 To be removed from the cluster once installed
Master-0 ocp4-master-0.minwi.lan 192.168.32.100
Master-1 ocp4-master-1.minwi.lan 192.168.32.101
Master-2 ocp4-master-2.minwi.lan 192.168.32.102
Worker-0 ocp4-worker-0.minwi.lan 192.168.32.200

NOTE: Those baremetal servers are Dell based, so racadm will be used in order to manage the iDRAC to map a virtual cd, power off/on, etc.

References

Steps

You can’t perform that action at this time.