This section describes the scenario of installing Cloud Pak for Applications first, followed by Cloud Pak for Integration.
From the experience of the residency group, if you are wanting to install these two Cloud Paks in this order in the same cluster, it is important to follow the instructions below to resolve conflicts and make things go smoothly
The first step is to consider the prerequisites for the Cloud Paks you want to install and to make sure your cluster has the required resources.
- Refer to the Knowledge Center prerequisites page (Cloud Pak for Applications 4.0.x) for details on what is required before starting an installation.
- Also consider the prerequisites for installing the Cloud Pak for Applications developer tools. Prerequisites and installation instructions are provided in this Playbook for Mac and for Windows workstations.
- Refer to the Knowledge Center prerequisites page (Cloud Pak for Integration 2019.4) for details on what is required before starting an installation.
For your convenenience, the combined resource requirements that were used during the residency in January 2020 are shown below. You are advised to check the product documentation for the most current numbers for the releases you want to install.
|Node Type||Quantity||CPU||RAM||DISK 1||DISK 2||DISK 3|
The instructions to install Cloud Pak for Integration are further down the page. Before you do that installation, read the following paragraphs to understand that your first installation attempt will fail. The following paragraphs describe the problem and the solution for you to complete your installation of Cloud Pak for Integration successfully.
Conflict with Installed Helm Component Issue:
Helm component is installed and used by Cloud Pak for Application.
The installation of Cloud Pak for Integration also includes the
component. At the time of writing, there was no built-in function in the
installer to deal with an already existing
When the Cloud Pak for Integration is trying to install
Helm on the same
cluster, and finds an existing Custom Resource Definition (CRD) with
a certificate for
Helm, the installation fails. Cloud Pak for Applications
and Cloud Pak for Integration share the same certificate, and the
Cloud Pak for Integration installer cannot tolerate the condition where
the certificate already exists.
Trying to complete an installation after a failed partial install will
result in failure of the IBM Cloud Pak (ICP) common services creation in
kube-system namespace, due to missing secrets.
The solution is to do a full uninstall of Cloud Pak for Integration after after your initial installation fails, and then to reinstall it. The uninstaller removes the common component and allows the reinstall to run without encountering the conflict.
It is possible that the uninstall might hang. You can check for and clear that condition by checking for pods in a terminating state and doing a force delete on them. Use the following command to see if you have pods stuck in a terminating state.
oc get pods --all-namespaces | grep Terminating
If you do find pods in that condition, use the following command on each such pod to do a force deletion.
oc delete pod <pod name> -n <project-name> --force --grace-period=0