Available Images

The DPOD Cloud Agent images are available on the following container registries:

• Operator images (Catalogcatalog, bundle and Operatoroperator) : icr.io/dpod (Does does not requires authenticated access)

• Application images (Managermanager, Messagingmessaging, Apiapi-proxy, Ingestersingesters): cp.icr.io/cp/dpod (Requires requires authenticated access, see : Getting access Access to images from Images on the public Public IBM Entitled Registry)

On the current version a mirroring from icr.io/cpopen → icr.io/dpod is required.

...

See Cloud Agent Overview for a list of available versions.

Choose the Appropriate Mirroring Procedure

The procedure for mirroring the Cloud Agent images varies, depending on the flavor of Kubernetes in you environment:

...

A private container registry

...

RedHat OpenShift Container Platform
(OCP)

...

Follow OCP

...

Getting Access to Images on the Public IBM Entitled Registry

The DPOD Cloud Agent images that are hosted on the IBM Entitled Registry (cp.icr.io/cp/dpod) require authenticated access. Use your entitlement key to create a pull secret, and use the pull secret in the DPOD Cloud Agent CR to allow the Cloud Agent Operator to pull these images. For more details, see Getting Access to Images on the Public IBM Entitled Registry.

Configuring Mirroring (Optional)

If the k8s cluster does not have access to the online registries, mirroring can be used with a local private registry which hosts the Cloud Agent images:

• For an example of mirroring configuration in RedHat OpenShift Container Platform (OCP), see Cloud Agent Mirroring - OCP (Optional).

• For an example of mirroring configuration in other Kuberenetes flavors (e.g.: AWS EKS, Azure AKS)

...

• , see Cloud Agent Mirroring - K8S (Optional).