Get started with Full observability (classic full stack deployment)
This page provides instructions for deploying the Dynatrace Operator in classic full stack configuration to a Kubernetes cluster.
Before you begin
Before installing Dynatrace on your Kubernetes cluster, ensure that you meet the following requirements:
- Your
kubectl
CLI is connected to the Kubernetes cluster that you want to monitor. - You have sufficient privileges on the monitored cluster to run
kubectl
oroc
commands.
Cluster setup and configuration
-
You must allow egress for Dynatrace pods (default: Dynatrace namespace) to your Dynatrace environment URL.
-
For OpenShift Dedicated, you need the cluster-admin role.
-
Helm installation Use Helm version 3.
Supported versions
See supported Kubernetes/OpenShift platform versions and distributions.
Installation options
Choose one of the installation methods that best suits your needs.
Helm
Dynatrace Operator version 0.8.0+
New Helm installation and upgrade instructions use our Helm chart available from an OCI registry. Therefore, if the Dynatrace repository is currently added to your local Helm repositories, it can be safely removed.
helm repo remove dynatrace
The installation process is independent of whether you are using Kubernetes or OpenShift. The platform is auto-detected during the installation.
-
Install Dynatrace Operator
The following command works for both default installations and installations using an OCI registry.
helm install dynatrace-operator oci://public.ecr.aws/dynatrace/dynatrace-operator \--set csidriver.enabled="false" \--create-namespace \--namespace dynatrace \--atomic \Edit the
values.yaml
 sample from GitHub, and then run the install command, passing the YAML file as an argument:Make sure to disable the CSI driver from being rolled out, as it's not used in classic fullstack.
csidriver:enabled: falsehelm install dynatrace-operator oci://public.ecr.aws/dynatrace/dynatrace-operator \--create-namespace \--namespace dynatrace \--atomic \-f values.yamlIf
installCRD
is set tofalse
, you need to create the custom resource definition manually before starting the Helm installation:kubectl apply -f https://github.com/Dynatrace/dynatrace-operator/releases/download/v1.3.0/dynatrace-operator-crd.yaml -
Create secret for access token
Create a secret named
dynakube
for the Dynatrace Operator token obtained in Tokens and permissions required.kubectl -n dynatrace create secret generic dynakube --from-literal="apiToken=<OPERATOR_TOKEN>" -
Apply the DynaKube custom resource
Download the DynaKube custom resource sample for classic full stack from 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 45sIn 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-2wnbb 1/1 Running 0 50sdynakube-oneagent-wp2bt 1/1 Running 0 50sdynakube-oneagent-pxdv4 1/1 Running 0 50sdynatrace-operator-8445c87f87-qhc5t 1/1 Running 0 3m02sdynatrace-webhook-56644487df-ws7gg 1/1 Running 0 3m02sdynatrace-webhook-56644487df-xkxkd 1/1 Running 0 3m02sAs OneAgent is deployed as DaemonSet, you should have a OneAgent pod on each node.
Manifest
Learn more
After you've successfully installed the Dynatrace Operator, you may find the following resources helpful for further learning and troubleshooting.
Get actionable answers
Start to analyze your Kubernetes clusters and containerized Apps with Dynatrace and benefit from actionable answers.
Guides
Learn how you can configure Dynatrace Operator to support specific use cases.
Troubleshooting
Troubleshoot any challenges you may encounter while working with the Dynatrace Operator and its various components.
How it works
Want to learn more about the Dynatrace components in your Kubernetes cluster?
Reference
API reference and configuration options for all Dynatrace components within your Kubernetes cluster.
Dynatrace Operator release notes
See release notes for Dynatrace Operator.
Update or uninstall
This page provides a detailed instructions on how to update and uninstall Dynatrace Operator.