Mirroring images to a private container registry (Upgrading from Version 4.7.x to a later 4.7 refresh)

If you mirrored the images for IBM Cloud Pak® for Data Version 4.7.x to a private container registry, you must mirror the images for the 4.7 refresh that you want to install to the private container registry before you upgrade your installation.

Upgrade phase
You are not here. Updating your client workstation
You are not here. Collecting required information
You are here icon. Preparing to run an upgrade from a private container registry
You are not here. Upgrading shared cluster components
You are not here. Upgrading an instance of Cloud Pak for Data
Who needs to complete this task?

Registry administrator A registry administrator or someone with the appropriate permissions to push images to the private container registry must complete this task.

When do you need to complete this task?

If you use a private container registry, you must complete the appropriate task for your environment.

If you have multiple instances of Cloud Pak for Data on your cluster, you can either:

  • One-time setup Minimize the number of times you mirror the software images by:
    1. Identifying all of the instances of Cloud Pak for Data on the cluster.
    2. Identifying all of the components that are installed in each instance.
    3. Specifying all of the components for all of the instances when you mirror the images.
  • Repeat as needed Mirror the images for one instance at a time.

Before you begin

Ensure that your private container registry meets the Private container registry requirements.

About this task

There are several ways that you can mirror images from the IBM® Entitled Registry to your private container registry. Choose the most appropriate method for your environment by answering the following question:

Can you set up a client workstation that can connect to the internet and the private container registry?

Yes
You can mirror the images directly from the IBM Entitled Registry to the private container registry.
No, the private container registry is in a restricted network
You must mirror the images to an intermediary container registry before you can mirror the images to the private container registry.
The cpd-cli manage mirror-images command automatically sets up an intermediary container registry on the client workstation. You must be able to move the intermediary container registry behind your firewall. For example, you can use:
Options Details
Use a portable compute device, such as a laptop, that you can move behind your firewall.
You can use the same device to:
  • Mirror images from the IBM Entitled Registry to the intermediary container registry.
  • Mirror images from the intermediary container registry to the private container registry.
Use a portable storage device, such as a USB drive, that you can move behind your firewall.
You must set up two client workstations:
  • A workstation that can connect to the internet. From this workstation, you can mirror the images from the IBM Entitled Registry to the intermediary container registry on the portable storage device.
  • A workstation that can connect to the private container registry. After you move the portable storage device to this workstation, you can mirror the images from the intermediary container registry to the private container registry.
Use a file transfer protocol, such as scp or sftp, to move images behind your firewall.
You must set up two client workstations:
  • A workstation that can connect to the internet. From this workstation, you can mirror the images from the IBM Entitled Registry to the intermediary container registry.
  • A workstation that can connect to the private container registry. After you transfer the intermediary container registry to this workstation, you can mirror the images from the intermediary container registry to the private container registry.

Procedure

Complete the appropriate task to mirror images to your private container registry: