Planning and Installation
Domain 2 tests planning and installation: prerequisites, sizing, storage, and the cpd-cli workflow. Questions often present a constraint and ask which prerequisite is violated.
Prerequisites to verify
- Supported OpenShift version and architecture.
- Enough worker nodes, CPU, memory, and ephemeral storage for the control plane plus each service.
- A default storage class that supports the access modes each service requires; many services need ReadWriteMany.
- DNS, certificates, and outbound connectivity for entitlement and image pulls.
- Entitlement key and registry access.
Installation flow
Create the operator namespace, install the platform operator, run cpd-cli manage setup-instance to create the control plane, then install services with cpd-cli manage install-components. Confirm with cpd-cli manage status and get-cpd-instance-details. Sizing is cumulative: control plane overhead plus every service’s profile.
Worked example
A plan includes Db2 Warehouse and Watson Studio on three workers with a ReadWriteOnce-only storage class. The likely failure is not CPU but storage access: Db2 and Studio expect volumes that can be mounted by multiple pods. Choose a storage class that supports RWX and confirm IOPS, not just capacity.
Traps
Treating the minimum node count as sufficient for all services. Forgetting that image pulls and backups consume storage. Installing services before the control plane is healthy. Using a namespace name that the scripts do not expect.