Location of images

Images for IBM Cloud Pak® for Integration are stored in online container registries:

  • IBM Cloud Container Registry

  • IBM Entitled Registry

  • Red Hat Quay.io

To use these registries, you must ensure they are accessible from your cluster nodes.

IBM Cloud® Container Registry and IBM Entitled Registry

IBM Cloud Container Registry hosts IBM® software container images. The IBM Entitled Registry is a namespace of the IBM Cloud Container Registry, where image permissions are linked to the software entitlement associated with IBM IDs. The IBM Entitled Registry contains images that require license entitlement to pull and run. Pulling images from the IBM Entitled Registry requires an entitlement key. For information on obtaining your entitlement key and applying it to your cluster as a pull secret, see Applying your entitlement key by using the UI (online installation).

The cpopen namespace hosts operator images that can be pulled without authentication. This enables you to configure clusters for use with IBM Cloud Pak for Integration without having to supply an entitlement key. An entitlement key is required only when deploying instances.

The appc-dev namespace hosts images for IBM App Connect Enterprise for Developers. These images can be pulled without authentication.

Images

  • IBM Cloud Pak for Integration operators

  • IBM Operator Catalog

  • IBM Cloud Pak foundational services Operator Catalog

  • All images that require entitlement to pull and run. This includes images used when deploying instances using the operators.

Network information:

  • Network flows must be open for TCP/IP traffic to the cp.icr.io and icr.io hosts on the https (443) port.

Red Hat Quay.io

Quay.io is a public container registry that hosts publicly accessible images, as well as private repositories. For more information see the Red Hat Quay.io documentation.

Images IBM images in Quay.io are in the namespace quay.io/opencloudio:

  • Images for IBM Cloud Pak foundational services

  • Images for CouchDB

Network information

  • Network flows must be open for TCP traffic to the quay.io host on the https (443) port.