Compatibility of classicFullStack with the AWS EKS Auto Mode? OneAgent DaemonSets failing

[DanielS]

Hi everyone,

I'm currently validating the  AWS EKS Auto Mode 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 DynaKube).

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.

The Situation:

• What works: 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.

• The Problem: The OneAgent DaemonSets consistently fail to initialize, crash-loop, or fail to schedule onto the managed EKS Auto Mode nodes.

My Configuration & Troubleshooting:

• I am using the classicFullStack configuration parameter within the DynaKube Custom Resource.

• ActiveGate connects fine, but the OneAgent pods never reach a healthy Running state.

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.

My Questions for the Community:

1. Is classicFullStack currently supported on AWS EKS Auto Mode, or does the node abstraction introduce an architectural compatibility gap?

2. Should I switch to the cloudNativeFullStack or applicationMonitoring approach for this specific managed infrastructure?

3. Has anyone successfully bypassed this, or is there a known workaround/upcoming support for EKS Auto Mode?

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.

Thanks in advance!