Cloud Native Full Stack: Workloads require manual restart after full OpenShift cluster reboot to get Deep Monitoring

[deni]

Hi,

I'm observing a reproducible behavior in an OpenShift cluster monitored with Dynatrace Cloud Native Full Stack and would like to understand whether this is expected or if others have seen something similar.

Environment

• OpenShift 4.19

• Dynatrace Operator 1.8.1

• Cloud Native Full Stack enabled

• Dynatrace CSI Driver running

• Dynatrace Webhook running

• ActiveGate running

What happens

After a full cluster shutdown/startup, the cluster comes back healthy and workloads start successfully.

However, multiple processes appear in Dynatrace as:

• Restart required

• Failed to enable

Examples include:

• Spring Boot application workloads

• kube-apiserver

• kubelet

• openshift-apiserver

• etcd-related processes

Application workload example

For our Spring Boot application we verified the following:

Immediately after cluster startup:

• Application pod is running

• Service is reachable

• Process appears in Dynatrace

• Deep Monitoring is not fully active

• Dynatrace reports Restart required

After performing a rollout restart of the deployment:

• /opt/dynatrace/oneagent-paas is mounted

• OneAgent libraries are loaded

• Deep Monitoring becomes enabled

• Services and process details appear correctly

What makes this interesting

This is not a one-time occurrence.

We can reproduce it after every full cluster reboot:

1. Shut down the entire cluster.

2. Start the cluster again.

3. Workloads start successfully.

4. Dynatrace reports multiple processes as Restart required.

5. Manual pod restart fixes application workloads.

Additional observation

Some processes occasionally disappear from Host → Processes view while remaining visible and active in Process Group view. Opening the host through the process relationship sometimes makes the process visible again.

Question

Has anyone seen similar behavior with Cloud Native Full Stack after a complete OpenShift cluster restart?

Is it expected that workloads may start before the Dynatrace CSI driver/webhook are fully ready, requiring a restart to receive Deep Monitoring?

Are there any recommended practices to ensure workloads are instrumented automatically after cluster recovery without requiring manual rollout restarts?

Thanks!

Regards, Deni