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.
In https://ibm.github.io/cloud-pak-deployer/50-advanced/private-registry-and-air-gapped/, images are mirrored to a private or portable registry. Some customers will not allow to run Cloud Pak Deployer to run in their environment and in these cases we have to revert to cpd-cli, which requires the olm-utils-v2 image to be available in the private registry.
[x] Include olm-utils-v2:latest as a tar file in the status directory
[x] Include olm-utils:latest as a tar file in the status directory
[ ] in the air-gapped installation, reference the CP4D documentation and adjustments to be made for cpd-cli
In https://ibm.github.io/cloud-pak-deployer/50-advanced/private-registry-and-air-gapped/, images are mirrored to a private or portable registry. Some customers will not allow to run Cloud Pak Deployer to run in their environment and in these cases we have to revert to
cpd-cli, which requires theolm-utils-v2image to be available in the private registry.olm-utils-v2:latestas a tar file in the status directoryolm-utils:latestas a tar file in the status directory