Red Hat OpenShift Deployment Guide
1. Prerequisites
Before deploying OpenShift, ensure the following prerequisites are met:
✓ 3+ physical or virtual servers for control plane (masters) with minimum 4 CPUs, 16
✓ Worker nodes with minimum 2 CPUs, 8 GB RAM per node (scalable to desired
GB RAM each.
✓ DNS records (A and PTR) for all nodes (api.<domain>, *.apps.<domain>).
capacity).
✓ Load balancer for control plane (API server) and router ingress.
✓ Internet or Red Hat Satellite access for subscription and image pulls.
✓ Valid Red Hat OpenShift and RHEL subscriptions.
✓ Shared NTP and synchronized time across all nodes.
✓ Passwordless SSH from bootstrap/control node to all hosts.
2. Deployment Tools
The following tools are used:
✔ OpenShift Installer CLI (openshift-install)
✔ OpenShift Client CLI (oc)
✔ Red Hat CoreOS or RHEL 8/9 nodes (for user-managed installations)
✔ Ansible (optional for automation)
✔ DNS, Load Balancer, and DHCP infrastructure
3. Installation Modes
Choose one of the following installation types:
a. Installer-Provisioned Infrastructure (IPI): Fully automated installation (requires AWS,
Azure, vSphere etc.)
b. User-Provisioned Infrastructure (UPI): Manual node and infra setup (recommended
for bare metal/on-prem)
4. Deployment Steps (User-Provisioned Infrastructure - Bare Metal)
1. Step 1: Download openshift-install and oc CLI from Red Hat Customer Portal.
2. Step 2: Generate the install-config.yaml using `openshift-install create install-config`.
3. Step 3: Configure DNS records and load balancer (HAProxy, F5 etc.).
4. Step 4: Manually provision RHCOS/RHEL nodes and assign IPs (static or DHCP
reservations).
5. Step 5: Place ignition files via HTTP server and boot nodes with ignition config.
6. Step 6: Bootstrap node initiates cluster creation and master/worker join automatically.
7. Step 7: Monitor installation via `openshift-install wait-for install-complete`.
8. Step 8: Access OpenShift web console at https://console-openshift-
console.apps.<domain>.
9. Step 9: Configure cluster-wide storage, image registry, logging, and monitoring.
10. Step 10: Install Operators and Management Hub tools (e.g., GitLab, Jenkins, Prometheus,
etc.).
5. Post-Installation Configuration
✔ Configure persistent storage (ODF, Ceph, NFS).
✔ Setup identity provider (LDAP, SSO, GitHub OAuth).
✔ Apply security policies (network, pod, SCCs).
✔ Enable monitoring and alerting stack.
✔ Deploy CI/CD pipelines, backup policies, and registry mirroring.
6. Validation & Testing
Run the following tests:
✓ Verify HA failover for API and Ingress endpoints.
✓ Test pod scheduling and resource scaling.
✓ Validate image registry builds and CI pipelines.
✓ Confirm logs and metrics collection (EFK and Prometheus).
✓ Simulate DR restore with Velero.
7. Cluster Backup & Maintenance
Establish regular backup routines using Velero or etcd snapshots. Perform routine
maintenance including:
• Weekly health checks (nodes, pods, PVCs)
• Monthly update planning and testing on staging clusters
• Quarterly Red Hat subscription sync and patch review
• Annual disaster recovery drills