Setting up a private registry
Before you begin
The steps in the Procedure section must be run in your private registry and not on the OpenShift Container Platform cluster that is used for the Cloud Pak for Business Automation deployment. Examples of private registries are Sonotype Nexus repository and JFrog Artifactory.
About this task
Make sure that your image registry meets the following requirements:
- Supports Docker Manifest V2, Schema 2.
- Supports multi-architecture images.Note: Do not use the Red Hat OpenShift image registry as your private registry. The Red Hat OpenShift registry does not support multi-architecture images.
- Is accessible from both the host and your OpenShift Container Platform cluster nodes.
- Has the username and password of a user who can write to the target registry from the host.
- Has the username and password of a user who can read from the target registry that is on the OpenShift Container Platform cluster nodes.
- Allows path separators in the image name.
To pull all of the images, you need at least 500 GB of disk space. The actual size does depend on the registry type that you are using because some registries require more storage than other types of registry. All the images in the groups are pulled irrespective of architecture.
When the images are mirrored to your private registry, the namespaces where images are mirrored must exist or the image push must create them automatically. If your registry does not allow automatic creation of namespaces, you must create them manually. If you do need to create the namespaces manually, create the following namespaces at the root of your registry.
Procedure
What to do next
- Supports auto-repository creation.
- Has credentials of a user who can write and create repositories. The host uses these credentials.
- Has credentials of a user who can read all repositories. The OpenShift Container Platform cluster uses these credentials.
You can now set up the image inventory. For more information, see Downloading the CASE files and cert-kubernetes.
- Create a path or folder in the target registry. For example,
myregistry/cp4ba-<version>
. - Make sure that you specify this path when generating the mirror manifests and mirroring the images.
- Make sure that the generated
ImageContentsourcePolicy
(image-content-source-policy.yaml
) has the correct path. - Mirror the images of the new version or interim fix. All images are mirrored to
myregistry/cp4ba-<version>
. - Make sure that the deployment is upgraded to the new version or interim fix.
After the upgrade is complete and all the images are upgraded to the new version or interim fix, you can now delete the images from the previous version.