Option 1: Mirroring catalogs to a private registry using oc mirror
You need to mirror the catalogs from a public registry to a private registry to install Cloud Pak for Business Automation for an airgap deployment.
Before you begin
After an upgrade, you can remove images from the previous version from the target registry by
creating a new path or folder to copy the images to instead of the default path. For example, the
following command mirrors the image to a specific folder (locationX) in the private registry instead
of the default
path:
oc ibm-pak generate mirror-manifests $CASE_NAME $TARGET_REGISTRY/locationX \ --version $CASE_VERSIONAbout this task
The custom resource file must use the default settings for the
sc_image_repository parameter in an air gap environment. The running pods show
the public image addresses even though the private registry is being used.
Tip: If the
catalogs fail to load from the private registry, the request uses the public registry. The public
registry request always fails in an airgap environment, so these errors might be misleading if you
focus on the public registry request.
Choose the type of host that you want to set up. Your choice determines how you mirror the
catalogs to the private registry. A portable compute device can be used with or without the use of a
portable storage device.
Important: You must set up an airgap environment for testing,
quality assurance (QA), and user acceptance testing (UAT). These environments can help to ensure
that the software is error-free before you roll the same tested Cloud Pak operator version or
interim fix out to a production environment. You must use the same bastion host, portable compute
device, or portable storage device to mirror all of the tested catalogs in all your deployment
environments. When testing is complete in your test/QA/UAT environments and you are ready to roll
the deployment out to production do not mirror the catalogs again. Mirroring the catalogs again
pulls the latest versions of Cloud Pak foundational services. These catalogs might be different from
what you tested in your test, QA, UAT, or pre-production environments.