Preparing a client to connect to the cluster

You must make sure that the client that you intend to use to connect to the OpenShift cluster has all the necessary tools.

About this task

A Red Hat OpenShift Kubernetes Service (ROKS) cluster and a private OpenShift cluster have different requirements. Make sure that the client can connect to the cluster you want to use, and has the necessary CLI tools. Install the appropriate tools from the following list.

Client-side requirements
Table 1. Client-side requirements step by step
Requirement More information
Kubernetes 1.21+ CLI For more information, see

You must use a kubectl version that is within one minor version difference of your cluster. Using the latest version of kubectl helps avoid unforeseen issues. Download the latest release with the command:

export KUBECTL_VERSION=`curl \
curl -LO "\

Use the chmod command to give access to kubectl and make it executable for all users.

chmod a+x kubectl

To check the version, run the following command.

kubectl version --client

Place the kubectl binary in a directory that is on your PATH. To check your PATH, run the following command.

echo $PATH
OCP CLI For more information, see the OpenShift 4.10 documentation and go to the download link. Download the latest version for your OCP cluster.

The CLI has commands for managing your applications, and lower-level tools to interact with each component of your system.

Place the oc binary in a directory that is on your PATH. To check your PATH, run the following command.

echo $PATH

When the CLI is in your PATH, it is available by running the oc command.

Podman CLI If you plan to download the Cloud Pak images to a private registry, you must install the Podman CLI. You can install Podman by running the following command.
yum -y install podman
Note: The podman CLI is needed on an OCP registry, as OCP does not support a Docker login. If you plan to run the scripts on macOS or you want to stick with docker, you must install the Docker CLI and add the following line to the /etc/docker/deamon.json file.
Where route is the name of the route for your image registry. For example, { "insecure-registries":["default-route-openshift-image-registry.apps.<hostname>"] }.

Use this solution for isolated testing or in tightly controlled environments only. For more information, see Deploy a plain HTTP registry.

cert-kubernetes Download the cert-kubernetes repository.
Note: Releases with interim fixes are packaged in archives with a new minor version. The version numbers follow the release.major.minor standard. For example, the first interim fix for 22.0.2 is packaged in the archive ibm-cp-automation-4.1.1.tgz. All available and future interim fixes provide an associated CASE package. To find the relevant instructions, go to the interim fix readme file.
  1. Download the 22.0.2 package by clicking Container Application Software for Enterprises (CASE) package 4.1.0, or go to the CASE packages URL and download the package for a specific or the latest interim fix.
    wget <case_package_url>
  2. Extract the package.
    tar -xvzf ibm-cp-automation-4.1.0.tgz
    cd ibm-cp-automation/inventory
    cd cp4aOperatorSdk/files/deploy/crs
    tar -xvf cert-k8s-22.0.2.tar
What else is needed before you run the installation scripts
Table 2. Script requirements
Requirement More information
Operating system The scripts can be used only on amd64/x86 based (CentOS Stream/RHEL/MacOS) VM/machines. The scripts cannot be used on s390x/ppc64le machines. However, you can run the scripts on an amd64/x86 machine that connects to a Linux on Z or a Linux on Power based cluster.

What to do next

Go to and complete the next step in Preparing a namespace for the Cloud Pak operator.