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

Operator images (Catalog, bundle and Operator) : icr.io/dpod (Does not requires authenticated access)
Application images (Manager, Messaging, Api-proxy, Ingesters): cp.icr.io/cp/dpod (Requires authenticated access see: Getting access to images from the public IBM Entitled Registry)

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

Without a proper mirroring, the pods will fail on ImagePullBackOff error when trying to pull the images.

See Cloud Agent Overview for a list of available versions.

Image Name and Tag

Image Name and Tag
dpod-cloud-agent-operator-catalog:<OPERATOR-VERSION>-amd64
dpod-cloud-agent-operator-bundle:<OPERATOR-VERSION>-amd64
dpod-cloud-agent-operator:<OPERATOR-VERSION>-amd64
dpod-cloud-agent-api-proxy:<DPOD-VERSION>-amd64
dpod-cloud-agent-http-ingester:<DPOD-VERSION>-amd64
dpod-cloud-agent-manager:<DPOD-VERSION>-amd64
dpod-cloud-agent-messaging-broker:<DPOD-VERSION>-amd64
dpod-cloud-agent-syslog-ingester:<DPOD-VERSION>-amd64

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

	A private container registry
RedHat OpenShift Container Platform (OCP)	Follow OCP
Other Kuberenetes flavors (e.g.: AWS EKS, Azure AKS)	Follow K8S

IBM DPOD v1.0.21.x