book

Red Hat OpenShift on IBM Z and LinuxONE Cookbook

by Lydia Parziale, Anilkumar Patil, Rakesh Krishnakumar, Shrirang Kulkarni, Li Liyong, Victor Recio, Srirama Sharma, Richard Young

July 2024

Intermediate to advanced

156 pages

4h 14m

English

IBM Redbooks

Read now

Unlock full access

Trademarks
AuthorsNow you can become a published author, too!Comments welcomeStay connected to IBM Redbooks
1.1 Red Hat OpenShift overview1.2 Red Hat OpenShift on IBM Z and LinuxONE1.2.1 Red Hat OpenShift capabilities on IBM Z and LinuxONE1.2.2 Red Hat OpenShift benefits on IBM Z or LinuxONE1.2.3 Red Hat OpenShift deployment options on IBM Z and LinuxONE
2.1 Red Hat OpenShift components overview2.2 Red Hat OpenShift components and their roles2.2.1 Bootstrap node2.2.2 Control plane2.2.3 Compute Node2.2.4 Bastion node
3.1 Red Hat OpenShift product deployment requirements3.1.1 Load balancer3.1.2 Network Configuration Management3.1.3 Bastion host3.1.4 Hosting hypervisor environment3.2 Number of hosting logical partitions for a cluster3.3 Deployment architectures used in this paper3.3.1 Single-LPAR deployment configuration3.3.2 Three-LPAR deployment configuration3.4 Storage architecture3.4.1 FCP-attached SCSI and FICON-attached ECKD storage3.4.2 CoreOS node storage3.4.3 RHEL virtual server disk storage3.4.4 Red Hat OpenShift Persistent Storage3.5 Multitenancy with other workloads3.5.1 LPAR level controls in IBM Z and LinuxONE3.5.2 Guest controls in KVM3.5.3 Guest controls in IBM z/VM3.6 Recovery site considerations3.7 IBM Secure Execution3.8 IBM CEX high-performance hardware security modules requirements3.9 FIPS requirements3.10 Multus for a second network interface3.11 Authenticating3.12 Monitoring3.13 Logging
4.1 LPAR adjustments and weights4.1.1 General LPAR adjustments4.1.2 IBM z/VM weights4.1.3 Adjustments for Red Hat OpenShift
5.1 Deployment topology criteria5.1.1 Data gravity5.1.2 Consolidation and TCO Reduction5.1.3 Business continuity5.1.4 Vertical Solutions5.2 IBM z/VM One LPAR cluster implementation5.2.1 Resource planning5.2.2 DNS configuration5.2.3 HAPROXY configuration5.2.4 Ignition files and the HTTP server5.2.5 USER DIRECT and PARM files for OCP nodes5.2.6 Building the Red Hat OpenShift Container Platform cluster5.2.7 Using Ansible playbooks5.3 IBM z/VM three-LPAR cluster implementation5.3.1 Architecture5.3.2 Planning resources5.3.3 HAPROXY configuration5.3.4 USER DIRECT and PARM files for OCP nodes5.3.5 Building the OCP cluster5.4 KVM single hypervisor cluster implementation5.4.1 Architecture5.4.2 Planning resources5.4.3 DNS configuration5.4.4 Ansible controller configuration5.4.5 Load balancer configuration5.4.6 File server for Ansible Playbook5.4.7 Building the OCP cluster through Ansible5.4.8 Validating the deployment5.5 KVM three-LPAR cluster implementation5.5.1 Architecture5.5.2 Hypervisor preparation5.5.3 DNS server configuration5.5.4 DHCP server configuration5.5.5 Highly available load balancer configuration5.5.6 Rapidly creating the guests that provide the support infrastructure5.5.7 Creating the Red Hat OpenShift cluster5.5.8 Completing the initial installation of Red Hat OpenShift 4.12
6.1 Applying best practices6.1.1 CPU entitlement and vCPU number6.1.2 Disabling transparent huge pages6.1.3 Enabling RFS6.1.4 Infrastructure nodes6.1.5 HyperPAV6.1.6 Specific for KVM6.2 Post-installation configurations6.2.1 Defining an identity provider6.2.2 Configuring persistent storage6.2.3 Configuring the NTP Server6.2.4 Disabling kubeadmin6.2.5 Backing up the etcd database6.3 Sample application deployment6.3.1 Application architecture6.3.2 Deployment
Locating the web materialUsing the web material