Prerequisites

Components impacted 

Prior to installation

• Cloud Pak for Automation Operator: cp.icr.io/cp/cp4a/icp4a-operator:20.0.3-IF004
• Business Automation Workflow: cp.icr.io/cp/cp4a/baw/workflow-server:20.0.3-IF004
• Business Automation Workflow Authoring： cp.icr.io/cp/cp4a/bas/workflow-authoring:20.0.3-IF004

Installing

1. Log in to MyIBM Container Software Library with the IBMid and password that is associated with the entitled software.
2. In the Container software library tile, click "View library" and then click "Copy key" to copy the entitlement key to the clipboard.
3. Log in to your Kubernetes cluster and set the context to the project/namespace for your existing deployment.
4. Create a pull secret by running a kubectl create secret command.
   $ kubectl create secret docker-registry admin.registrykey --docker-server=cp.icr.io --docker-username=cp --docker-password="<API_KEY_GENERATED>" --docker-email=<USER_EMAIL>
   Note: The "cp.icr.io" value for the docker-server parameter is the only registry domain name that contains the images. Use "cp" for the docker-username. The docker-email must be a valid email address (associated to your IBM ID). Make sure you are copying the Entitlement Key in the docker-password field within double quotation marks.
5. Take a note of the secret and the server values so that you can set them to the "pullSecrets" and "repository" parameters when you update the operator for your containers.

1. Log in to your Kubernetes cluster and set the context to the project for your existing deployment.
   $ oc login https://<CLUSTERIP>:<port> -u <ADMINISTRATOR>
2. If the persistent volume (PV) for the operator is defined by a hostPath, provide group write permission according to the PV hostPath.path definition (/root/operator).
   $ chmod -R g=u /root/operator
   $ chmod g+rw /root/operator
   Note: If you are using dynamic provisioning, this step is not needed as the PV is created automatically as per the Storage Class definition.
3. Remove the .OPERATOR_TYPE file in case it exists from a previous deployment.
   $ rm -f /<hostPath>/.OPERATOR_TYPE
   Where hostPath is the value in your PV (root/operator).
4. Go to the downloaded cert-kubernetes folder for the IF002 interim fix.
5. Upgrade the operator in your project by running the following command.

   $ ./scripts/upgradeOperator.sh -i <registry_url>/icp4a-operator:20.0.3-IF003 -p '<my_secret_name>' -a accept

   Where registry_url is the value for your internal registry or cp.icr.io/cp/cp4a for the IBM Cloud Entitled Registry. The my_secret_name is the secret that is created to access the registry, and accept means that you accept the license.

   Note: If you plan to use a non-admin user to install the operator, you must add the user to the "ibm-cp4a-operator" role.

   $ oc adm policy add-role-to-user ibm-cp4a-operator <user_name>
6. Monitor the pod until it shows a STATUS of Running:
   $ oc get pods -w
   Note: When started, you can monitor the operator logs with the following command:
   $ oc logs -f deployment/ibm-cp4a-operator -c operator

  workflow_authoring_configuration:
    images:
      repository: "cp.icr.io/cp/cp4a/bas/workflow-authoring"
      tag: "20.0.3-IF004"

baw_configuration:
- name: bawins1
    case:
      init_job_image:
        repository: "cp.icr.io/cp/cp4a/baw/workflow-server"
        tag: "20.0.3-IF004"

• Cloud Pak for Automation Operator
• Business Automation Workflow