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)
See Cloud Agent Overview for a list of available versions.
Image Name | Image 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 |
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.
For an example of mirroring configuration in other Kuberenetes flavors (e.g.: AWS EKS, Azure AKS), see Cloud Agent Mirroring - K8S.