This page gives an overview and documents the different configurations for all major Kubernetes distributions.
For the overall Dynatrace support lifecycle for Kubernetes and Red Hat OpenShift, including the currently supported versions, see Dynatrace support lifecycle for Kubernetes and Red Hat OpenShift full stack Monitoring.
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
No specific configuration is required for EKS.
Dynatrace supports a variety of different flavors of AWS EKS. For EKS on EC2 or bare metal, you can install Dynatrace in any available deployment option without any additional configuration changes. For EKS on Fargate, you can install Dynatrace for App Observability.
applicationMonitoring
Additional configuration is required for AWS Bottlerocket OS on EKS nodes. You can deploy Dynatrace for Application Observability and configure Platform Observability via ActiveGate (Kubernetes API Monitoring). Platform Observability via Dynatrace OneAgent is not supported. Starting with Dynatrace Operator version 0.12.0, the CSI-driver is supported and needs to be configured in read-only mode for Bottlerocket OS:
apiVersion: dynatrace.com/v1beta2kind: DynaKubemetadata:name: dynakubenamespace: dynatraceannotations:feature.dynatrace.com/automatic-kubernetes-api-monitoring: "true"feature.dynatrace.com/injection-readonly-volume: "true"spec:apiUrl: https://ENVIRONMENTID.live.dynatrace.com/apioneAgent:applicationMonitoring:useCSIDriver: trueactiveGate:capabilities:- routing- kubernetes-monitoring- dynatrace-api...
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
No specific configuration is required for AKS.
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
No specific configuration is required for GKE.
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
If you deploy Dynatrace in classicFullStack
or hostMonitoring
without the CSI driver, additional configuration is required. Enable volume storage for the OneAgent by setting the ONEAGENT_ENABLE_VOLUME_STORAGE
environment variable:
apiVersion: dynatrace.com/v1beta2kind: DynaKubemetadata:name: dynakubenamespace: dynatracespec:apiUrl: https://ENVIRONMENTID.live.dynatrace.com/apioneAgent:classicFullStack:env:- name: ONEAGENT_ENABLE_VOLUME_STORAGEvalue: "true"...
applicationMonitoring
For GKE Autopilot, you can install Dynatrace for App Observability. The CSI driver is supported for all GKE Autopilot clusters running Kubernetes version 1.26+. Additionally, only images from the following repositories are supported and must be set during installation:
gcr.io/dynatrace-marketplace-prod/dynatrace-operator:v1.3.2
docker.io/dynatrace/dynatrace-operator:v1.3.2
Depending on the deployment option, the image can be set in different ways.
The CSI driver included in Dynatrace Operator version 1.3.0+ is currently under security review by Google. We expect to receive allowlisting approval by mid-October 2024. In the meantime, if you require the CSI driver, use Dynatrace Operator version 1.2.2.
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
Classic full-stack is supported only on Kubernetes nodes that use Red Hat Enterprise Linux (RHEL) as their operating system.
For OpenShift, you need to configure Security Context Constraints (SCC) for all deployments using the Dynatrace CSI driver (cloudNativeFullStack
, applicationMonitoring
/hostMonitoring
with CSI). In addition, starting with Openshift 4.13, you need to configure the CSI Inline Ephemeral Volume Admissing plugin.
For OpenShift Dedicated, you need the cluster-admin role.
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
No specific configuration is required for RKE.
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
For TKGI, additional environment configurations are required for all deployment modes except applicationMonitoring
without the CSI driver.
cloudNativeFullStack
, applicationMonitoring
(with CSI driver), and hostMonitoring
Additional configuration is required for these modes to configure the CSI driver:
csidriver:enabled: truekubeletPath: "/var/vcap/data/kubelet"
classicFullStack
Requires images from the Dynatrace built-in registry and not from the public registry. Use the following configuration:
oneAgent:classicFullStack:env:- name: ONEAGENT_ENABLE_VOLUME_STORAGEvalue: "true"- name: ONEAGENT_CONTAINER_STORAGE_PATHvalue: /var/vcap/store
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
For IKS, additional environment configurations are required for all deployment modes except applicationMonitoring
without the CSI driver.
cloudNativeFullStack
, applicationMonitoring
(with CSI driver), and hostMonitoring
Additional configuration is required for these modes to configure the CSI driver:
csidriver:enabled: truekubeletPath: "/var/data/kubelet"
classicFullStack
Requires images from the Dynatrace built-in registry and not from the public registry. Use the following configuration:
oneAgent:classicFullStack:env:- name: ONEAGENT_ENABLE_VOLUME_STORAGEvalue: "true"- name: ONEAGENT_CONTAINER_STORAGE_PATHvalue: /opt
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
If you deploy Dynatrace in classicFullStack
or hostMonitoring
without the CSI driver, be sure to configure volume storage for OneAgent:
apiVersion: dynatrace.com/v1beta2kind: DynaKubemetadata:name: dynakubenamespace: dynatracespec:apiUrl: https://ENVIRONMENTID.live.dynatrace.com/apioneAgent:classicFullStack: # change to `hostMonitoring` if neededenv:- name: ONEAGENT_ENABLE_VOLUME_STORAGEvalue: "true"
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
No specific configuration is required.
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
No specific configuration is required.
cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring
No specific configuration is required.