Configuration-based installation of OpenShift and Cloud Pak for Data/Integration/Watson AIOps on various private and public cloud infrastructure providers. Deployment attempts to achieve the end-state defined in the configuration. If something fails along the way, you only need to restart the process to continue the deployment.
However, when running an OpenShift cluster on Satellite, we run into a MachineConfigPool, unless ibm-roks is specified explicitly as the infrastructure type:
TASK [cp-ocp-mco-pause : Fail if MachineConfigPool worker does not exist and not IBM Cloud] ***
task path: /cloud-pak-deployer/automation-roles/50-install-cloud-pak/cpfs/cp-ocp-mco-pause/tasks/pause-mco.yml:27
Tuesday 12 December 2023 02:44:32 +0000 (0:00:00.030) 0:07:18.134 ******
fatal: [localhost]: FAILED! => changed=false
msg: MachineConfigPool worker does not exist, it should be if not installing on IBM Cloud ROKS
We could determine whether the cluster is a Satellite one using the following StorageClasses:
Describe the solution you'd like
In file
retrieve-openshift-type-existing-ocp.yml, the deployer is already able to detect whether a cluster is of type ibm-roks, was-rosa, or aws-self-managed.However, when running an OpenShift cluster on Satellite, we run into a
MachineConfigPool, unlessibm-roksis specified explicitly as the infrastructure type:We could determine whether the cluster is a Satellite one using the following StorageClasses:
sat-ocs-cephfs-goldsat-ocs-cephfs-gold-metrosat-ocs-cephrbd-goldsat-ocs-cephrbd-gold-metrosat-ocs-cephrgw-goldsat-ocs-noobaa-gold