Preparing for a starter deployment

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.

1. Set the required version to an environment variable:

   export KUBECTL_VERSION=`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`

2. Download the latest release with the command for your VM/machine architecture:

   Linux® on AMD x86-64 or amd64

   curl -LO "https://storage.googleapis.com/kubernetes-release/release/${KUBECTL_VERSION}/bin/linux/amd64/kubectl"

   Linux on Power® or ppc64le

   curl -LO "https://storage.googleapis.com/kubernetes-release/release/${KUBECTL_VERSION}/bin/linux/ppc64le/kubectl"

   Linux on IBM Z® or s390x

   curl -LO "https://storage.googleapis.com/kubernetes-release/release/${KUBECTL_VERSION}/bin/linux/s390x/kubectl"

   MacOS on amd64

   curl -LO "https://storage.googleapis.com/kubernetes-release/release/${KUBECTL_VERSION}/bin/darwin/amd64/kubectl"

   MacOS on arm64

   curl -LO "https://storage.googleapis.com/kubernetes-release/release/${KUBECTL_VERSION}/bin/darwin/arm64/kubectl"

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

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.

Tip: Use the move right arrow below the 26.0.0 release to find all the available interim fixes.

To download the cert-kubernetes repository.

1. Open the Cloud Pak for Business Automation download document , find the card for the latest 26.0.0 interim fix, click Cert Kubernetes, and then select and copy the displayed command.
2. Run the copied git clone command to download the files.

1. Log in to MyIBM Container Software Library with the IBMid and password that is associated with the entitled software.
2. In the Entitlement Keys tile, click Add New Key.

Before you deploy an automation container on IBM Cloud (your target cluster platform is ROKS), you must configure your client environment and create an OpenShift cluster.

Make sure that you install the IBM Cloud CLI so you can use the command-line interfaces (CLIs). As an administrator of the cluster you must be able to interact with your environment.

1. If you do not have an account, create an account on IBM Cloud .
2. If you do not have a cluster, then create one. From the IBM Cloud Overview page, in the OpenShift Cluster tile, click Create Cluster. Refer to the IBM Cloud documentation to create a Kubernetes cluster. The cluster that you create includes attached storage.
3. Log in to your ROKS cluster from a Linux VM on which you installed the OCP CLI.

   oc login --token=<token> --server=https://<cluster-ip>:<port>

   Where the <token> is your API token for your user on the cluster, and <cluster-ip>:<port> is the IP address and port number of the cluster. You can get these values by clicking Copy Login Command in the OCP console. The following example command shows that the token is an almost-unique fixed-size 256-bit (32-byte) hash.

   oc login --token=sha256~5a0GogeS4oEUfG5yFCcPE2Qf-rz5exEUiFaZ4V0Iy1Y \
   --server=https://api.ocp4616-cp4ba.cp.example.com:6443
   

Create a namespace for the Cloud Pak deployment on the OpenShift cluster. The Cloud Pak operator can be installed in multiple namespaces. You can create a namespace in the console or create one from the CLI.

On the left panel in your OpenShift console, click Administration > Namespaces, then click Create Namespace. In the Create Namespace dialog, specify a name for the namespace, for example cp4ba-starter. To use the default Network Policy, make sure that you select "No restrictions".

On the CLI:

oc login --token=<token> --server=https://<cluster-ip>:<port>
export NAMESPACE=<CP4BA deployment namespace>
oc create namespace ${NAMESPACE} 

Where the <CP4BA deployment namespace> is the namespace where you want to create the deployment. For example, cp4ba-starter.

1. Move to a directory where you want to put the temp files.

   cd /home/user

2. Install the htpasswd command.

   yum install httpd-tools

3. Create a user.

   htpasswd -c -B -b users.htpasswd [username] [password]

   Replace [username] with the name of the non-admin user. Replace [password] with the password for the non-admin user.

4. Verify that it worked.

   htpasswd -b -v users.htpasswd [username] [password]

5. Create a secret to contain the htpasswd file. You must be logged in as the admin user to the cluster.

   oc create secret generic htpass-secret --from-file=htpasswd=./users.htpasswd -n openshift-config

6. Create a config file with the htpasswd identity provider settings.

   cat <<EOF | oc apply  -f -
       apiVersion: config.openshift.io/v1
       kind: OAuth
       metadata:
         name: cluster
       spec:
        identityProviders:
        - name: admins_htpasswd_provider
          mappingMethod: claim
          type: HTPasswd
          htpasswd:
            fileData:
              name: htpass-secret  
   EOF

7. Verify that it worked. It might take a few minutes for the update to complete.

   oc logout
   oc login -u [username] -p [password]

For more information about users on OpenShift, see Understanding identity provider configuration .

Tip: Go to the following technote for instructions on how to create a simple identity provider for your starter environment How do I create a simple identity provider .

For more information, see Storage considerations.

yum -y install podman

"insecure-registries":["route"]

{
"insecure-registries":["default-route-openshift-image-registry.apps.<hostname>"]
}

For more information, see Creating custom-bai-secret.