topic OneAgent pod failing after Dynatrace Operator upgrade to v1.8.1 in Container platforms

OneAgent pod failing after Dynatrace Operator upgrade to v1.8.1

dhruv881 — Wed, 22 Apr 2026 07:05:02 GMT

We recently upgraded the Dynatrace Operator to v1.8.1 on OpenShift. After the upgrade OneAgent pods are failing to start and remain in Init:ErrImagePull / ImagePullBackOff state. From the documentation, we understand that newer operator versions add an init container to the OneAgent pods, which appears to be pulling the dynatrace-operator:v1.8.1 image.

The failure is due to an image pull timeout from registry.connect.redhat.com (i/o timeout on port 443), which suggests a network or registry access limitation on worker nodes. The operator pod itself is running, but the OneAgent init container cannot pull the required image.

Re: OneAgent pod failing after Dynatrace Operator upgrade to v1.8.1

AntonPineiro — Wed, 22 Apr 2026 08:55:33 GMT

Hi,

I would open a support case.

Best regards

Re: OneAgent pod failing after Dynatrace Operator upgrade to v1.8.1

Julius_Loman — Wed, 22 Apr 2026 09:56:01 GMT

I'd explore the node pull options on your case , see https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/guides/deployment-and-configuration/node-image-pull . I had similar issue a while ago on one environment. But the answer is complex and depends on your environment and setup.