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 to images from the public IBM Entitled Registry)
...
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 | 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 |
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
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)
...
Follow 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.