https://community.dynatrace.com/t5/Container-platforms/Compatibility-of-classicFullStack-with-the-AWS-EKS-Auto-Mode/m-p/300231#M3538 <P>Hi everyone,</P><P>I'm currently validating the&nbsp;&nbsp;<A href="https://docs.aws.amazon.com/eks/latest/userguide/automode.html" target="_blank" rel="noopener"><STRONG>AWS EKS Auto Mode</STRONG></A> in our staging environment (Kubernetes v1.29+) and running into blocking issues when trying to deploy the OneAgent via the Dynatrace Operator (v1.9.0, using the v1beta6&nbsp;DynaKube).</P><P>I have extensive experience deploying the Dynatrace Operator across standard EKS clusters without any issues, but EKS Auto Mode seems to introduce a roadblock for the OneAgent.</P><H3>The Situation:</H3><UL><LI><P><STRONG>What works:</STRONG> The Dynatrace Operator deploys successfully. Platform Observability via ActiveGate works perfectly, and our cluster API visibility/AWS account is fully visible in the Dynatrace UI.</P></LI><LI><P><STRONG>The Problem:</STRONG> The OneAgent DaemonSets consistently fail to initialize, crash-loop, or fail to schedule onto the managed EKS Auto Mode nodes.</P></LI></UL><H3>My Configuration &amp; Troubleshooting:</H3><UL><LI><P>I am using the classicFullStack configuration parameter within the DynaKube Custom Resource.</P></LI><LI><P>ActiveGate connects fine, but the OneAgent pods never reach a healthy Running state.</P></LI></UL><P>Since AWS EKS Auto Mode abstracts, automates, and restricts a lot of the underlying node infrastructure and control plane management, I suspect there might be specific permission constraints, taints, or runtime restrictions blocking the classic deployment pattern.</P><H3>My Questions for the Community:</H3><OL><LI><P>Is classicFullStack currently supported on AWS EKS Auto Mode, or does the node abstraction introduce an architectural compatibility gap?</P></LI><LI><P>Should I switch to the cloudNativeFullStack or applicationMonitoring approach for this specific managed infrastructure?</P></LI><LI><P>Has anyone successfully bypassed this, or is there a known workaround/upcoming support for EKS Auto Mode?</P></LI></OL><P>Any insights, official documentation links, or shared experiences would be highly appreciated, as this is currently blocking our production rollout strategy for EKS Auto Mode.</P><P>Thanks in advance!</P> Tue, 02 Jun 2026 15:07:05 GMT DanielS 2026-06-02T15:07:05Z https://community.dynatrace.com/t5/Container-platforms/Compatibility-of-classicFullStack-with-the-AWS-EKS-Auto-Mode/m-p/300231#M3538 <P>Hi everyone,</P><P>I'm currently validating the&nbsp;&nbsp;<A href="https://docs.aws.amazon.com/eks/latest/userguide/automode.html" target="_blank" rel="noopener"><STRONG>AWS EKS Auto Mode</STRONG></A> in our staging environment (Kubernetes v1.29+) and running into blocking issues when trying to deploy the OneAgent via the Dynatrace Operator (v1.9.0, using the v1beta6&nbsp;DynaKube).</P><P>I have extensive experience deploying the Dynatrace Operator across standard EKS clusters without any issues, but EKS Auto Mode seems to introduce a roadblock for the OneAgent.</P><H3>The Situation:</H3><UL><LI><P><STRONG>What works:</STRONG> The Dynatrace Operator deploys successfully. Platform Observability via ActiveGate works perfectly, and our cluster API visibility/AWS account is fully visible in the Dynatrace UI.</P></LI><LI><P><STRONG>The Problem:</STRONG> The OneAgent DaemonSets consistently fail to initialize, crash-loop, or fail to schedule onto the managed EKS Auto Mode nodes.</P></LI></UL><H3>My Configuration &amp; Troubleshooting:</H3><UL><LI><P>I am using the classicFullStack configuration parameter within the DynaKube Custom Resource.</P></LI><LI><P>ActiveGate connects fine, but the OneAgent pods never reach a healthy Running state.</P></LI></UL><P>Since AWS EKS Auto Mode abstracts, automates, and restricts a lot of the underlying node infrastructure and control plane management, I suspect there might be specific permission constraints, taints, or runtime restrictions blocking the classic deployment pattern.</P><H3>My Questions for the Community:</H3><OL><LI><P>Is classicFullStack currently supported on AWS EKS Auto Mode, or does the node abstraction introduce an architectural compatibility gap?</P></LI><LI><P>Should I switch to the cloudNativeFullStack or applicationMonitoring approach for this specific managed infrastructure?</P></LI><LI><P>Has anyone successfully bypassed this, or is there a known workaround/upcoming support for EKS Auto Mode?</P></LI></OL><P>Any insights, official documentation links, or shared experiences would be highly appreciated, as this is currently blocking our production rollout strategy for EKS Auto Mode.</P><P>Thanks in advance!</P> Tue, 02 Jun 2026 15:07:05 GMT https://community.dynatrace.com/t5/Container-platforms/Compatibility-of-classicFullStack-with-the-AWS-EKS-Auto-Mode/m-p/300231#M3538 DanielS 2026-06-02T15:07:05Z