Update or uninstall Dynatrace Operator
This page provides detailed instructions on how to update or uninstall Dynatrace Operator in Kubernetes and OpenShift environments.
Dynatrace Operator manages the deployment and lifecycle of all Dynatrace components in your Kubernetes clusters (for example, OneAgent, ActiveGate, and code modules). This includes, depending on the configuration, automatic updates for these components. Dynatrace Operator itself needs to be updated either by applying new manifests or by using helm charts.
We recommend using an up-to-date Operator version (at least version n-2) and always using the latest patch version of that Operator version (for example, 0.10.4 instead of 0.10.0).
Update Dynatrace Operator
To update Dynatrace Operator, select one of the following options, depending on your deployment approach:
Manifest
For classicFullStack, applicationMonitoring, or hostMonitoring, execute the following command.
If you're using the CSI driver, there's an additional prerequisite command:
Helm
-
Update your Helm repositories.
helm repo update dynatrace -
Upgrade the Helm chart.
helm upgrade dynatrace-operator oci://public.ecr.aws/dynatrace/dynatrace-operator \--namespace dynatrace \--atomic \-f values.yamlThe
values.yamlfile may have changed in newer versions. If existing values are no longer valid, they will be silently ignored as there's no validation for this.To upgrade to the latest release from the OCI registry, run the following command.
helm upgrade dynatrace-operator dynatrace/dynatrace-operator \--namespace dynatrace \--atomic \-f values.yamlNote that the
helm repocommand does not support OCI registries. You can only use thehelm pull,helm show,helm install, andhelm upgradecommands with OCI.Upgrade from old Dynatrace Operator versions with Helm
If you use a Dynatrace Operator version earlier than v0.8.0 in a Helm deployment, follow the steps below to migrate to the latest Dynatrace Operator version with Helm.
Upgrade the custom resource definition According to your configuration of the
values.yamlfile, select one of the options below.-
If
installCRDis set totrue, the custom resource definition will be automatically upgraded and managed by Helm. -
If
installCRDis set tofalse, you need to upgrade the custom resource definition manually before starting the Helm installation:
Upgrade the Helm chart Delete the CRD section and the secrets from your existing values.yaml file or use and customize the
values.yamlsample from GitHub. Upgrade the helm chart:helm upgrade dynatrace-operator dynatrace/dynatrace-operator -f values.yaml --atomic -n dynatraceThe above changes make your old values unusable, therefore setting the
--reuse-valuesflag isn't possible for migration. -
Update OneAgent if automatic updates are disabled
By default, Dynatrace Operator handles OneAgent updates automatically. If you choose to disable automatic updates, and haven't set any standard OneAgent version in Dynatrace, you can manually update OneAgent by running the command below.
Update Access tokens
If you need to update your Dynatrace access tokens, follow the steps below.
Find current tokens
Delete your secret
Create new tokens
Create a new secret with updated tokens
Delete the old tokens
Find current access tokens
Find and save your currently used tokens.
After generating new tokens, you'll need to delete the old ones.
Delete your secret
To delete the secret, run one of the commands below.
In Kubernetes, used tokens are stored in a secret named dynakube by default. If the DynaKube custom resource has a different name, or the tokens field in DynaKube is set, make sure that the new secret has the same name as defined there.
Create new access tokens
For instructions on how to create the tokens, see Access tokens and permissions.
Create a new secret with updated access tokens
To create a new secret with the updated tokens, run one of the commands below, making sure to replace the placeholders with the new tokens.
Dynatrace Operator picks up the updated secrets in approximately five minutes. Removing DynaKube and reapplying it forces an instant reconciliation.
Delete the old access token
After the new tokens are in place, delete the old ones.
- In Dynatrace, go to Access Tokens and look for the old token.
- Select Delete.
Uninstall Dynatrace Operator
To uninstall Dynatrace Operator, select one of the following options (Manifest or Helm), depending on your deployment approach.
Important for CRI-O Runtime users with classicFullStack
OneAgent version 1.279 and below
If you're using CRI-O as your cluster's container runtime with classicFullStack, complete the steps outlined in Migrate from classic to cloud-native full-stack mode as part of the uninstallation process.
Manifest
Select one of the following options (with or without CSI driver) to uninstall Dynatrace Operator.
Without CSI driver
-
Delete Dynatrace Operator.
-
Delete the namespace.
With CSI driver
-
Clean up DynaKube resources.
-
Wait until Dynatrace Operator components have been deleted.
-
Restart your monitored applications.
-
Clean up CSI driver resources.
-
Uninstall Dynatrace Operator.
-
Delete the namespace.
Helm
Select one of the following options (with or without CSI driver) to uninstall Dynatrace Operator.
Without CSI driver
-
Delete Dynatrace Operator.
helm uninstall dynatrace-operator -n dynatrace -
Delete the namespace.
With CSI driver
-
Clean up DynaKube resources.
-
Wait until Dynatrace Operator components have been deleted.
-
Restart your monitored applications.
-
Uninstall Dynatrace Operator.
helm uninstall dynatrace-operator -n dynatrace -
Delete the namespace.