https://community.dynatrace.com/t5/Container-platforms/Applying-persistent-host-group-settings-to-ROSA-worker-nodes/m-p/296957#M3510 <P class="">We're running a ROSA (Red Hat OpenShift Service on AWS) environment where worker nodes are frequently spun up and down. We need two specific settings applied to these nodes:</P><OL class=""><LI><STRONG>Disk alert suppression</STRONG> – A commonly used Linux directory on these hosts is intentionally kept at capacity by design, causing false-positive low disk alerts due to our global alert settings.</LI><LI><STRONG>Graceful shutdown alert suppression</STRONG> – Since these nodes are expected to be regularly terminated and recreated, we want to ignore graceful shutdown alerts for them specifically.</LI></OL><P class="">The problem is that any host-level settings we apply are lost when a node is recycled, the best solution I can think of is to assign these a host-group when they are created, which would allow the settings to persist. However, I'm unsure how to configure the Dynatrace Operator to automatically assign all worker nodes in this ROSA environment to a host group when they are created.</P><P class="">Is there a way to define a host group for all worker nodes via the Dynatrace Operator in a ROSA environment, so that the correct settings are consistently applied regardless of node churn?</P> Mon, 30 Mar 2026 21:39:51 GMT Greg_Marwick 2026-03-30T21:39:51Z https://community.dynatrace.com/t5/Container-platforms/Applying-persistent-host-group-settings-to-ROSA-worker-nodes/m-p/296957#M3510 <P class="">We're running a ROSA (Red Hat OpenShift Service on AWS) environment where worker nodes are frequently spun up and down. We need two specific settings applied to these nodes:</P><OL class=""><LI><STRONG>Disk alert suppression</STRONG> – A commonly used Linux directory on these hosts is intentionally kept at capacity by design, causing false-positive low disk alerts due to our global alert settings.</LI><LI><STRONG>Graceful shutdown alert suppression</STRONG> – Since these nodes are expected to be regularly terminated and recreated, we want to ignore graceful shutdown alerts for them specifically.</LI></OL><P class="">The problem is that any host-level settings we apply are lost when a node is recycled, the best solution I can think of is to assign these a host-group when they are created, which would allow the settings to persist. However, I'm unsure how to configure the Dynatrace Operator to automatically assign all worker nodes in this ROSA environment to a host group when they are created.</P><P class="">Is there a way to define a host group for all worker nodes via the Dynatrace Operator in a ROSA environment, so that the correct settings are consistently applied regardless of node churn?</P> Mon, 30 Mar 2026 21:39:51 GMT https://community.dynatrace.com/t5/Container-platforms/Applying-persistent-host-group-settings-to-ROSA-worker-nodes/m-p/296957#M3510 Greg_Marwick 2026-03-30T21:39:51Z https://community.dynatrace.com/t5/Container-platforms/Applying-persistent-host-group-settings-to-ROSA-worker-nodes/m-p/297210#M3511 <P>Have you tried setting the following in your dynakube?</P><LI-CODE lang="markup">... spec: apiUrl: https://ENVIRONMENTID.live.dynatrace.com/api oneAgent: # Optional: Set a host group for OneAgent # hostGroup: "MyHostGroup" ...</LI-CODE><P>Regards.</P> Thu, 02 Apr 2026 15:21:23 GMT https://community.dynatrace.com/t5/Container-platforms/Applying-persistent-host-group-settings-to-ROSA-worker-nodes/m-p/297210#M3511 dannemca 2026-04-02T15:21:23Z