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)

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.

AWS Bottlerocket OS

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/v1beta2
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)

cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring

No specific configuration is required for AKS.

Google Kubernetes Engine (GKE)

cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring

No specific configuration is required for GKE.

GKE Standard & Anthos

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/v1beta2
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

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:

Depending on the deployment option, the image can be set in different ways.

Red Hat OpenShift

cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring

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)

cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring

No specific configuration is required for RKE.

VMware Tanzu Kubernetes Grid Integrated Edition (TGKI)

cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring

For TGKI, additional environment configurations are required for all deployment modes except applicationMonitoring without the CSI driver.

The following steps configure the CSI driver to use the correct kubelet path. The change depends on the chosen installation method.

IBM Kubernetes Service (IKS)

cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring

For IKS, additional environment configurations are required for all deployment modes except applicationMonitoring without the CSI driver.

The following steps configure the CSI driver to use the correct kubelet path. The change depends on the chosen installation method.

SUSE Container as a Service (CaaS)

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/v1beta2
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

cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring

No specific configuration is required.

Oracle Kubernetes Engine (OKE)

cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring

No specific configuration is required.

Mirantis Kubernetes Engine

cloudNativeFullStack classicFullStack applicationMonitoring hostMonitoring

No specific configuration is required.