<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Cloud Native Full Stack: Workloads require manual restart after full OpenShift cluster reboot to get Deep Monitoring in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Cloud-Native-Full-Stack-Workloads-require-manual-restart-after/m-p/300508#M39155</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;H3&gt;Environment&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;OpenShift 4.19&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace Operator 1.8.1&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Cloud Native Full Stack enabled&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace CSI Driver running&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace Webhook running&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;ActiveGate running&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;What happens&lt;/H3&gt;&lt;P&gt;After a &lt;STRONG&gt;full cluster shutdown/startup&lt;/STRONG&gt;, the cluster comes back healthy and workloads start successfully.&lt;/P&gt;&lt;P&gt;However, multiple processes appear in Dynatrace as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Restart required&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Failed to enable&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Examples include:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Spring Boot application workloads&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;kube-apiserver&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;kubelet&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;openshift-apiserver&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;etcd-related processes&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;Application workload example&lt;/H3&gt;&lt;P&gt;For our Spring Boot application we verified the following:&lt;/P&gt;&lt;P&gt;Immediately after cluster startup:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Application pod is running&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Service is reachable&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Process appears in Dynatrace&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Deep Monitoring is not fully active&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace reports &lt;STRONG&gt;Restart required&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;After performing a rollout restart of the deployment:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;/opt/dynatrace/oneagent-paas is mounted&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;OneAgent libraries are loaded&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Deep Monitoring becomes enabled&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Services and process details appear correctly&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;What makes this interesting&lt;/H3&gt;&lt;P&gt;This is not a one-time occurrence.&lt;/P&gt;&lt;P&gt;We can reproduce it after every full cluster reboot:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Shut down the entire cluster.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Start the cluster again.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Workloads start successfully.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace reports multiple processes as &lt;STRONG&gt;Restart required&lt;/STRONG&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Manual pod restart fixes application workloads.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;H3&gt;Additional observation&lt;/H3&gt;&lt;P&gt;Some processes occasionally disappear from &lt;STRONG&gt;Host → Processes&lt;/STRONG&gt; view while remaining visible and active in &lt;STRONG&gt;Process Group&lt;/STRONG&gt; view. Opening the host through the process relationship sometimes makes the process visible again.&lt;/P&gt;&lt;H3&gt;Question&lt;/H3&gt;&lt;P&gt;Has anyone seen similar behavior with Cloud Native Full Stack after a complete OpenShift cluster restart?&lt;/P&gt;&lt;P&gt;Is it expected that workloads may start before the Dynatrace CSI driver/webhook are fully ready, requiring a restart to receive Deep Monitoring?&lt;/P&gt;&lt;P&gt;Are there any recommended practices to ensure workloads are instrumented automatically after cluster recovery without requiring manual rollout restarts?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Regards, Deni&lt;/P&gt;</description>
    <pubDate>Tue, 09 Jun 2026 18:20:28 GMT</pubDate>
    <dc:creator>deni</dc:creator>
    <dc:date>2026-06-09T18:20:28Z</dc:date>
    <item>
      <title>Cloud Native Full Stack: Workloads require manual restart after full OpenShift cluster reboot to get Deep Monitoring</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Cloud-Native-Full-Stack-Workloads-require-manual-restart-after/m-p/300508#M39155</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;H3&gt;Environment&lt;/H3&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;OpenShift 4.19&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace Operator 1.8.1&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Cloud Native Full Stack enabled&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace CSI Driver running&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace Webhook running&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;ActiveGate running&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;What happens&lt;/H3&gt;&lt;P&gt;After a &lt;STRONG&gt;full cluster shutdown/startup&lt;/STRONG&gt;, the cluster comes back healthy and workloads start successfully.&lt;/P&gt;&lt;P&gt;However, multiple processes appear in Dynatrace as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Restart required&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Failed to enable&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Examples include:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Spring Boot application workloads&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;kube-apiserver&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;kubelet&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;openshift-apiserver&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;etcd-related processes&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;Application workload example&lt;/H3&gt;&lt;P&gt;For our Spring Boot application we verified the following:&lt;/P&gt;&lt;P&gt;Immediately after cluster startup:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Application pod is running&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Service is reachable&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Process appears in Dynatrace&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Deep Monitoring is not fully active&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace reports &lt;STRONG&gt;Restart required&lt;/STRONG&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;After performing a rollout restart of the deployment:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;/opt/dynatrace/oneagent-paas is mounted&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;OneAgent libraries are loaded&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Deep Monitoring becomes enabled&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Services and process details appear correctly&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;H3&gt;What makes this interesting&lt;/H3&gt;&lt;P&gt;This is not a one-time occurrence.&lt;/P&gt;&lt;P&gt;We can reproduce it after every full cluster reboot:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Shut down the entire cluster.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Start the cluster again.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Workloads start successfully.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Dynatrace reports multiple processes as &lt;STRONG&gt;Restart required&lt;/STRONG&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Manual pod restart fixes application workloads.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;H3&gt;Additional observation&lt;/H3&gt;&lt;P&gt;Some processes occasionally disappear from &lt;STRONG&gt;Host → Processes&lt;/STRONG&gt; view while remaining visible and active in &lt;STRONG&gt;Process Group&lt;/STRONG&gt; view. Opening the host through the process relationship sometimes makes the process visible again.&lt;/P&gt;&lt;H3&gt;Question&lt;/H3&gt;&lt;P&gt;Has anyone seen similar behavior with Cloud Native Full Stack after a complete OpenShift cluster restart?&lt;/P&gt;&lt;P&gt;Is it expected that workloads may start before the Dynatrace CSI driver/webhook are fully ready, requiring a restart to receive Deep Monitoring?&lt;/P&gt;&lt;P&gt;Are there any recommended practices to ensure workloads are instrumented automatically after cluster recovery without requiring manual rollout restarts?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Regards, Deni&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jun 2026 18:20:28 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Cloud-Native-Full-Stack-Workloads-require-manual-restart-after/m-p/300508#M39155</guid>
      <dc:creator>deni</dc:creator>
      <dc:date>2026-06-09T18:20:28Z</dc:date>
    </item>
  </channel>
</rss>

