Setting up your registry server

To install IBM Certified Container Software for IBM Sterling Secure Proxy, you must have a registry server where you can host the image required for installation.

Using the existing registry server

If you have an existing registry server, you can use it, provided that it is in close proximity to cluster where you will deploy IBM Certified Container Software for IBM Sterling Secure Proxy. If your registry server is not in close proximity to your cluster, you might notice performance issues. Also, before the installation, ensure that pull secrets are created in the namespace/project and are linked to the service accounts. You will need to properly manage these pull secrets. This pull secret can be updated in values.yaml file `image.imageSecrets`.

Using Docker registry in Kubernetes cluster

Kubernetes does not provide a registry solution out of the based. However, you can create your own registry server and host your images. Please refer to the deployment of registry server.

Using 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 4.6: Integrated Red Hat OpenShift Container Platform registry

Ensure that you can access the registry externally:

For OpenShift 4.6: Exposing the registry