ocp4-upi-compute-powervs

The ocp4-upi-compute-powervs project provides Terraform based automation code to help with the deployment of OpenShift Container Platform (OCP) 4.x compute workers on IBM® Power Systems™ Virtual Server on IBM Cloud.

Warning Active code updates in progress to make the code base more resilient.

Prerequisites

1. Requires Terraform v1.5.0 to v1.5.5. You may use the alternative OpenTofu.
2. A IBM Cloud Workspace for Power Virtual Server on IBM Cloud that supports Power Edge Router. If your workspace supports s922,s1022,e980,e1080, you'll have to update the var.tfvars to the supported system_type.
3. An RHCOS Image loaded to the PowerVS Service
4. An IBM Cloud Transit Gateway connecting the IBM Cloud to your IBM Cloud VPC. The connections must be established.
5. Optional: An CentOS Stream 9 Image loaded to the PowerVS Service
6. An Existing OpenShift Container Platform Cluster installed on IBMCloud VPC with Intel architecture.

The bastion must be RHEL9 equivalent or higher.

Important Notes

1. The Automation Supports OVN-Kube networks only.
2. The terraform code deploys a dhcp sever on the bastion node.

Commands

Init

❯ terraform init -upgrade

Plan

Copy the var.tfvars into a sub-folder data/

Edit for your usage

❯ terraform plan -var-file=data/var.tfvars

Note: The PowerVS and IBMCloud VPC regions must be compatible.

Apply

❯ terraform apply -var-file=data/var.tfvars

Destroy

❯ terraform destroy -var-file=data/var.tfvars

Note, the destroy command removes the Node resource, removes the NFS deployment, and destroys the virtual servers. Please backup your NFS Server first - it is destroyed.

Cluster Details

There are some important points to mention:

1. The Power Bastion no longer uses an https proxy to forward requests to the Cluster's internal api load balancer. This setting is removed.
2. NFS is used as the storage provider across nodes.

Running Automation from another IBMCloud VPC

To run the code, you'll need to set the MTU for your machine:

ip link set eth0 mtu 1400

Getting the IPs of Power Workers

To get the IPs of the Power Workers.

❯ oc get nodes -l 'kubernetes.io/arch=ppc64le' -owide
NAME                STATUS   ROLES    AGE   VERSION           INTERNAL-IP      EXTERNAL-IP   OS-IMAGE                                                       KERNEL-VERSION                  CONTAINER-RUNTIME
mac-d263-worker-0   Ready    worker   40h   v1.27.4+4e87926   192.168.200.10   <none>        Red Hat Enterprise Linux CoreOS 414.92.202308151250-0 (Plow)   5.14.0-284.25.1.el9_2.ppc64le   cri-o://1.27.1-6.rhaos4.14.gitc2c9f36.el9

Contributing

If you have any questions or issues you can create a new [issue here][issues].

Pull requests are very welcome! Make sure your patches are well tested. Ideally create a topic branch for every separate change you make. For example:

1. Fork the repo
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

License

All source files must include a Copyright and License header. The SPDX license header is preferred because it can be easily scanned.

If you would like to see the detailed LICENSE click here.

#
# Copyright 2025 - IBM Corporation. All rights reserved
# SPDX-License-Identifier: Apache-2.0
#

Support

Is this a Red Hat or IBM supported solution?

Multi-Arch Compute with an Intel Control Plane and Intel/Power compute is not supported - Installer-Provisioned Infrastructure and User Provisioned nodes are not supported.