Prerequisites

Prerequisite information when deploying in IBM® Cloud Private.

When deploying the product in IBM® Cloud Private, ensure you have fulfilled the following prerequisites:

Docker version 18.03.1 or later.
Kubernetes 1.15 with Beta APIs enabled.
IBM Workload Automation containers run on x86_64 systems.
If dynamic provisioning is not being used, Persistent Volume must be re-created and setup with labels that can be used to refine the Kubernetes PVC bind process
If dynamic provisioning is being used, specify a storageClass per Persistent Volume provisioner to support dynamic volume provisioning
A default storageClass is setup during the cluster installation or created prior to the deployment by the Kubernetes administrator

Additional pre and post configuration scripts, instructions, files, samples, etc. might be placed in the ibm_cloud_pak/pak_extensions folder. The pak_extension folder contains two subdirectories that you can use for your extensions. The current structure is:

ibm_cloud_pak
           pak_extensions
               post-delete
                  clusterAdministration
                      deleteRolePSP.sh
                  namespaceAdministration
                      deleteRoleBinding.sh
               pre-install
                  clusterAdministration
                      createRolePSP.sh
                  namespaceAdministration
                      createRoleBinding.sh

Create a Role and a RoleBinding for the namespace (for further details, refer to the Readme specific for the component you're installing)
Create a DB instance and schema (Server and Console only; for further details, refer to the Readme specific for the component you're installing)
Create a mysecret.yaml file to store passwords (Server and Console only; for further details, refer to the Readme specific for the component you're installing)

Following you can find a table containing the system requirements for each container:

Table 1. IBM Workload Automation containers' system requirements
System Resource	Agent	Console	Sever
CPU	200m	2	2
Memory	200Mi	8Gi	8Gi
Storage	2Gi	5Gi	10Gi

For additional information about IBM® Cloud Private system requirements, refer to IBM® Cloud Private system requirements

Using the NFS server with persistent volumes

This section explains how to configure persistent volumes if you use the NFS server.

To avoid issues during the daily activity, it is highly suggested to configure the persistent volume to use the version 3 of the NFS server, and set the local lock parameter to all.

The following is an example of .yaml file that shows how to configure the persistent volume:

kind: PersistentVolume
apiVersion: v1
metadata:
  name: release_name-data
  labels:
    volname: volume_name
spec:
  capacity:
    storage: 15Gi
  accessModes:
    - ReadWriteOnce
  mountOptions:
    - nfsvers=3
    - local_lock=all
  nfs:
    path: nfs_server_path
    server: nfs_server_IPaddress

where:

volname is the same name specified in the Volume label name field during the deployment procedure.

volume_name is the same value specified in the Volume label value field during the deployment procedure.

15Gi is the same value specified in the PV minimum size field during the deployment procedure.