To use the Dynatrace Operator add-on for AWS Elastic Kubernetes Service (AWS EKS), you need to install the add-on and then connect EKS with your environment.
You can install the Dynatrace Operator add-on for AWS EKS through the AWS console or the CLI.
To install the Dynatrace Operator add-on for AWS EKS through the AWS console
Go to your EKS cluster.
In the Add-ons section, select Get more add-ons > AWS Marketplace add-ons.
Filter for category Monitoring or search for Dynatrace to find the Dynatrace Operator add-on.
Select the checkbox in the upper-right corner of the card and then select Next.
Optional Select the version for this add-on and IAM role.
Select Next and review the configuration before applying.
Select Create and wait for the operation to finish.
dynatrace namespace is createdTo install the Dynatrace Operator add-on for AWS EKS through the CLI
Check the availability of the add-on and its versions.
aws eks describe-addon-versions --addon-name dynatrace_dynatrace-operator
Deploy the add-on, specifying the version if necessary.
aws eks create-addon --cluster-name <your_cluster_name> --addon-name dynatrace_dynatrace-operator --addon-version <version>
Verify the successful installation.
aws eks describe-addon --cluster-name <your_cluster_name> --addon-name dynatrace_dynatrace-operator
Create secret for access tokens.
Create a secret named dynakube for the Dynatrace Operator token and data ingest token obtained in Tokens and permissions required.
kubectl -n dynatrace create secret generic dynakube --from-literal="apiToken=<OPERATOR_TOKEN>" --from-literal="dataIngestToken=<DATA_INGEST_TOKEN>"
Apply the DynaKube custom resource
Monitoring with cloudNativeFullStack or appOnly (with CSI driver) is only supported for Dynatrace Operator version 0.15.0+.
Download the DynaKube custom resource sample for cloud-native full-stack mode on GitHub. In addition, you can review the available parameters or how-to-guides, and adapt the DynaKube custom resource according to your requirements.
Run the command below to apply the DynaKube custom resource, making sure to replace <your-DynaKube-CR> with your actual DynaKube custom resource file name. A validation webhook will provide helpful error messages if there's a problem.
kubectl apply -f <your-DynaKube-CR>.yaml
Optional Verify deployment
Verify that your DynaKube is running and all Pods in your Dynatrace namespace are running and ready.
> kubectl get dynakube -n dynatraceNAME APIURL STATUS AGEdynakube https://<ENVIRONMENTID>.live.dynatrace.com/api Running 45s
In a default DynaKube configuration, you should see the following Pods:
> kubectl get pods -n dynatraceNAME READY STATUS RESTARTS AGEdynakube-activegate-0 1/1 Running 0 50sdynakube-oneagent-b88rn 1/1 Running 0 50sdynakube-oneagent-m5jm4 1/1 Running 0 50sdynakube-oneagent-qhd9u 1/1 Running 0 50sdynatrace-oneagent-csi-driver-qxfwx 4/4 Running 0 2m49sdynatrace-oneagent-csi-driver-xk5c4 4/4 Running 0 2m49sdynatrace-oneagent-csi-driver-mz6ch 4/4 Running 0 2m49sdynatrace-operator-7dc8dc7d8c-wmh4z 1/1 Running 0 2m59sdynatrace-webhook-7bb6957fb5-l8fsq 1/1 Running 0 2m59sdynatrace-webhook-7bb6957fb5-rqnqk 1/1 Running 0 2m59s
These steps apply to Amazon EKS with the Fargate launch type. To monitor Amazon ECS with the Fargate launch type instead, see Monitor AWS Fargate.
Kubernetes version 1.20+
On AWS Fargate, only the applicationMonitoring deployment without the CSI driver is supported.
Before you start installation, make sure you have a running AWS Fargate cluster. For details, see Getting started with AWS Fargate using Amazon EKS.
Add a Fargate profile to define the Dynatrace Operator deployment.
Be sure it matches the dynatrace namespace where Dynatrace Operator is deployed.
Create a dynatrace namespace.
kubectl create namespace dynatrace
Install Dynatrace Operator.
kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v1.9.0/kubernetes.yaml
Create the secret holding the API token for authentication to the Dynatrace Cluster.
kubectl -n dynatrace create secret generic dynakube --from-literal="apiToken=<API_TOKEN>"
Replace <API_TOKEN> with your own value.
Download the preconfigured DynaKube custom resource sample file from GitHub.
Review the available parameters, and adapt the DynaKube custom resource according to your requirements.
Apply the DynaKube custom resource.
kubectl apply -f applicationMonitoring.yaml