Supported distributions

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.

AWS Elastic Kubernetes Service (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.

If you are using AWS Bottlerocket OS on your 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:

yaml
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
  name: dynakube
  namespace: dynatrace
  annotations:
    feature.dynatrace.com/automatic-kubernetes-api-monitoring: "true"
    feature.dynatrace.com/injection-readonly-volume: "true"
  spec:
    apiUrl: https://ENVIRONMENTID.live.dynatrace.com/api
    oneAgent:
      applicationMonitoring:
        useCSIDriver: true
    activeGate:
      capabilities:
        - routing
        - kubernetes-monitoring
        - dynatrace-api
    ...

Azure Kubernetes Service (AKS)

No specific configuration is required for AKS.

Google Kubernetes Engine (GKE)

GKE Standard & Anthos

For Standard GKE clusters, you can install Dynatrace in any available deployment option. If you deploy Dynatrace in classicFullStack or hostMonitoring without the CSI driver, be sure to configure volume storage for OneAgent:

yaml
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
  name: dynakube
  namespace: dynatrace
  spec:
    apiUrl: https://ENVIRONMENTID.live.dynatrace.com/api
    oneAgent:
      classicFullStack:
        env:
        - name: ONEAGENT_ENABLE_VOLUME_STORAGE
          value: "true"
    ...

GKE Autopilot

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 or later. Additionally, only images from the following repositories are supported:

gcr.io/dynatrace-marketplace-prod/dynatrace-operator:<version>
docker.io/dynatrace/dynatrace-operator:<version>

The CSI driver included in Dynatrace Operator version 0.13.0 is currently under security review by Google. We expect to receive allowlisting approval by mid-October 2023. In the meantime, if you require the CSI driver, use Dynatrace Operator version 0.12.1.

Red Hat OpenShift

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.

Rancher Kubernetes Engine (RKE)

No specific configuration is required for RKE.

VMware Tanzu Kubernetes Grid Integrated Edition (TGKI)

For TGKI, additional environment configurations are required for all deployments that use OneAgent on Kubernetes nodes (classicFullStack, cloudNativeFullStack, hostMonitoring):

yaml
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
  name: dynakube
  namespace: dynatrace
  spec:
    apiUrl: https://ENVIRONMENTID.live.dynatrace.com/api
    oneAgent:
      classicFullStack: # change to `cloudNativeFullStack` or `hostMonitoring` if needed
        env:
        - name: ONEAGENT_ENABLE_VOLUME_STORAGE #not required for cloudNativeFullStack and hostMonitoring with CSI driver
          value: "true"
        - name: ONEAGENT_CONTAINER_STORAGE_PATH
          value: /var/vcap/store

IBM Kubernetes Service (IKS)

For IKS, additional environment configurations are required for all deployments that use OneAgent on Kubernetes nodes (classicFullStack, cloudNativeFullStack, hostMonitoring):

yaml
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
  name: dynakube
  namespace: dynatrace
  spec:
    apiUrl: https://ENVIRONMENTID.live.dynatrace.com/api
    oneAgent:
      classicFullStack: # change to `cloudNativeFullStack` or `hostMonitoring` if needed
        env:
        - name: ONEAGENT_ENABLE_VOLUME_STORAGE #not-required for cloudNativeFullStack and hostMonitoring with CSI driver
          value: "true"
        - name: ONEAGENT_CONTAINER_STORAGE_PATH
          value: /opt

SUSE Container as a Service (CaaS)

If you deploy Dynatrace in classicFullStack or hostMonitoring without the CSI driver, be sure to configure volume storage for OneAgent:

yaml
apiVersion: dynatrace.com/v1beta1
kind: DynaKube
metadata:
  name: dynakube
  namespace: dynatrace
  spec:
    apiUrl: https://ENVIRONMENTID.live.dynatrace.com/api
    oneAgent:
      classicFullStack: # change to `hostMonitoring` if needed
        env:
        - name: ONEAGENT_ENABLE_VOLUME_STORAGE
          value: "true"

D2iQ Convoy

No specific configuration is required.

Oracle Kubernetes Engine (OKE)

No specific configuration is required.

Mirantis Kubernetes Engine

No specific configuration is required.