Setting up your registry server
To install Cloud Pak for Data, you must have a registry server where you can host the images for the Cloud Pak for Data control plane and the services that you want to install.
- Using your existing registry server
- If you have an existing registry server, you can use it, provided that it is in close proximity to the Red Hat® OpenShift® cluster where you will deploy Cloud Pak for Data. If your registry server is not in close proximity to your OpenShift cluster, you might notice performance issues. Also, before the Cloud Pak for Data installation, ensure that pull secrets are created in the OpenShift project and are linked to the service accounts. You will need to properly manage these pull secrets.
- Using the Red Hat OpenShift internal registry
- Alternatively, you can use the internal registry in your Red Hat OpenShift cluster. This option is recommended
because it does not require you to manage pull secrets. For information on the internal registry, see:
- For OpenShift 3.11: Internal Registry Overview
- For OpenShift 4.5: Integrated Red Hat OpenShift Container Platform registry
- Refresh 2 or later For OpenShift 4.6: Integrated Red Hat OpenShift Container Platform registry
Ensure that you can access the registry externally:- For OpenShift 3.11: Securing and Exposing the Registry
- For OpenShift 4.5: Exposing the registry
- Refresh 2 or later For OpenShift 4.6: Exposing the registry
Important: If you are installing the Cloud Pak for Data Operator on an air-gapped
cluster, you must set up an internet-facing machine as a bastion node. For details, see: