Making the RSI image available from a private container registry

If your cluster pulls images from a private container registry, you must make the resource specification injection (RSI) image (zen-rsi-adm-controller) available from the private container registry.

Who needs to complete this task?: A user who has permissions to push images to the private container registry must complete this task.
When do you need to complete this task?: Complete this task if your cluster pulls images from a private container registry.
Skip this task if your cluster pulls images directly from the IBM® Entitled Registry.

Before you begin

Check whether another user has already moved the /cpd/zen-rsi-adm-controller:4.6.5-x86_64 image to the private container registry.

If the image is not in the private container registry, complete the following tasks before you move the images to the private container registry:

About this task

The RSI feature uses the zen-rsi-adm-controller image:

x86-64 clusters: icr.io/cpopen/cpd/zen-rsi-adm-controller:4.6.5-x86_64

Procedure

The steps that you must complete depend on whether the workstation can connect to both the internet and the private container registry at the same time:

The workstation can connect to the internet and to the private container registry

Ensure that Docker or Podman is running on the workstation.
Ensure that the olm-utils image is available on the client workstation:
```
cpd-cli manage restart-container
```
Log in to the private container registry.
The following command assumes that you are using private container registry that is secured with credentials:
```
cpd-cli manage login-private-registry \
${PRIVATE_REGISTRY_LOCATION} \
${PRIVATE_REGISTRY_PUSH_USER} \
${PRIVATE_REGISTRY_PUSH_PASSWORD}
```
If your private registry is not secured, see cpd-cli manage login-private-registry for additional options.

Run the following command to copy the zen-rsi-adm-controller image from the IBM Entitled Registry to the private container registry:

cpd-cli manage copy-image \
--from=icr.io/cpopen/cpd/zen-rsi-adm-controller:4.6.5-x86_64 \
--to=${PRIVATE_REGISTRY_LOCATION}/cpd/zen-rsi-adm-controller:4.6.5-x86_64

The workstation cannot connect to the private container registry at the same time

From a workstation that can connect to the internet:
1. Ensure that Docker or Podman is running on the workstation.
2. Ensure that the olm-utils image is available on the client workstation:
```
cpd-cli manage restart-container
```
3. Run the following command to save the zen-rsi-adm-controller image to the client workstation:
```
cpd-cli manage save-image \
--from=icr.io/cpopen/cpd/zen-rsi-adm-controller:4.6.5-x86_64
```
  This command saves the image as a compressed TAR file named icr.io_cpopen_zen-rsi-adm-controller_4.6.5_x86_64.tar.gz in the cpd-cli-workspace/olm-utils-workspace/work/offline directory.
Transfer the compressed file to a client workstation that can connect to the cluster.
Ensure that you place the icr.io_cpopen_zen-rsi-adm-controller_4.6.5_x86_64.tar.gz file in the cpd-cli-workspace/olm-utils-workspace/work/offline directory.
From the workstation that can connect to the cluster:
1. Ensure that Docker or Podman is running on the workstation.
2. Log in to the private container registry.
  The following command assumes that you are using private container registry that is secured with credentials:
```
cpd-cli manage login-private-registry \
${PRIVATE_REGISTRY_LOCATION} \
${PRIVATE_REGISTRY_PUSH_USER} \
${PRIVATE_REGISTRY_PUSH_PASSWORD}
```
  If your private registry is not secured, see cpd-cli manage login-private-registry for additional options.
3. Run the following command to copy the zen-rsi-adm-controller image to the private container registry:
```
cpd-cli manage copy-image \
--from=icr.io/cpopen/cpd/zen-rsi-adm-controller:v1.1 \
--to=${PRIVATE_REGISTRY_LOCATION}/cpd/zen-rsi-adm-controller:4.6.5-x86_64
```