Try it free

Install Dynatrace Operator add-on for Azure Kubernetes Service (AKS)

  • Latest Dynatrace
  • Published Mar 14, 2025

To use the Dynatrace Operator add-on for Azure Kubernetes Service (AKS), you need to install the add-on and then connect AKS with your environment.

Prerequisites

  • Create access tokens for the Dynatrace Operator token and data ingest token obtained in Tokens and permissions required.

Install Dynatrace Operator add-on for AKS through Azure Portal

  1. Go to Azure Portal.

  2. Search for AKS cluster in the search bar at the top and filter for Resources.

  3. Select the cluster.

  4. Go to Settings > Extensions + applications.

  5. Select Add or Install an extension, if you don't have any extensions installed yet.

  6. Search for Dynatrace and select Dynatrace Operator for Azure Kubernetes Services.

  7. Select Create on the next screen.

  8. On the Basics tab, select your AKS cluster from the drop-down list in AKS Cluster Name field.

  9. On the Dynatrace operator configuration tab, fill in the following values:

    • AKS extension resource name: dynatraceazuregrail.
    • Dynatrace operator token: token value from Operator token you created in prerequisites.
    • Data ingest token: token value from the data ingest token you created in prerequisites.
    • API URL: URL value will be https://<dtenvid>.live.dynatrace.com/api.
    • OneAgent Deployment Type: Select the appropriate OneAgent deployment type from the dropdown based on your observability needs. For more details on different on observability options, see Deployment.

  10. Select Review + Create and then Create on the next screen.

  11. After the deployment is complete, go to Dynatrace and search for Kubernetes Classic. You should see your cluster and some of the metrics start to show up.

Install Dynatrace Operator add-on for AKS through CLI

  1. To install the Dynatrace Operator for Azure AKS through the CLI, execute the following command:

    az k8s-extension create --name <extensionName> --scope cluster --cluster-name <AKSClusterName> --resource-group <azureResourceGroup> --cluster-type managedClusters --extension-type "dynatrace.azuredynatraceoperator.one.x" --plan-name "dynatrace-operator-1-x" --plan-product "azure-dynatrace-operator" --plan-publisher "dynatrace" --configuration-settings "dynatrace-operator-azure.apiurl=https://<DTEnvID>.live.dynatrace.com/api" "dynatrace-operator-azure.mode=cloudNativeFullStack" --config-protected-settings "dynatrace-operator-azure.apitoken=<dTAPIToken>" "dynatrace-operator-azure.dataingesttoken=<dataIngestToken>"

  2. To verify if the extension was installed successfully via the CLI, execute the following command:

    az k8s-extension show --name <extensioName> --cluster-name <aksClusterName> --resource-group <azureResourceGroup> --cluster-type managedClusters --query "provisioningState"

  3. Optional Verify that your DynaKube is running and all Pods in your Dynatrace namespace are running and ready.

    > kubectl get dynakube -n dynatrace
    NAME         APIURL                                          STATUS     AGE
    dynakube     https://<ENVIRONMENTID>.live.dynatrace.com/api  Running    45s

    In a default DynaKube configuration with CSI driver, you should see the following Pods:

    > kubectl get pods -n dynatrace
    NAME                                  READY   STATUS    RESTARTS        AGE
    dynakube-activegate-0                 1/1     Running   0               50s
    dynatrace-oneagent-csi-driver-qxfwx   4/4     Running   0               2m49s
    dynatrace-oneagent-csi-driver-xk5c4   4/4     Running   0               2m49s
    dynatrace-oneagent-csi-driver-mz6ch   4/4     Running   0               2m49s
    dynatrace-operator-7dc8dc7d8c-wmh4z   1/1     Running   0               2m59s
    dynatrace-webhook-7bb6957fb5-l8fsq    1/1     Running   0               2m59s
    dynatrace-webhook-7bb6957fb5-rqnqk    1/1     Running   0               2m59s

  4. Remove the extension.

    az k8s-extension delete --name <extensionName> --cluster-name <AKSClusterName> --resource-group <azureResourceGroup> --cluster-type managedClusters