e-minguez/ocp4-upi-bm-pxeless-staticips

Step by step guide to deploy OCP4 UPI on baremetal without PXE and with static IPs

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

• https://github.com/christianh814/openshift-toolbox/tree/master/ocp4_upi
• https://docs.openshift.com/container-platform/4.1/installing/installing_bare_metal/installing-bare-metal.html

Steps

• 0 - Prerequisites
• 1 - Variables
• 2 - Load balancer
• 3 - Web server
• 4 - DNS
• 5 - OpenShift files
• 6 - Cluster files
• 7 - Ignition files
• 8 - RHCOS files
• 9 - Modify ISOs
• 10 - Configure oc command
• 11 - Installation
• 12 - Post installation
• 13 - Upgrade
• 14 - Verification
• 99 - Tips and tricks