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

Helm

Manifest

For classicFullStack, applicationMonitoring, or hostMonitoring, execute the following command.

If you're using the CSI driver, there's an additional prerequisite command:

Helm

To update Dynatrace Operator, you need to upgrade the Helm chart. Run the command below.

1helm upgrade dynatrace-operator dynatrace/dynatrace-operator -f values.yaml --atomic -n dynatrace

The values.yaml file 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.

1helm upgrade dynatrace-operator oci://docker.io/dynatrace/dynatrace-operator --reuse-values --atomic --namespace=dynatrace

1helm upgrade dynatrace-operator dynatrace/dynatrace-operator -f values.yaml --atomic -n dynatrace

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.

Migrate from classicFullStack to cloudNativeFullStack with CRI-O runtime

OneAgent version 1.279 and earlier

If you're using CRI-O as your cluster's container runtime and you want to transition from classicFullStack to cloudNativeFullStack, follow the steps outlined below.

Uninstall Dynatrace Operator

To uninstall Dynatrace Operator, select one of the following options (Manifest or Helm), depending on your deployment approach.

Manifest

Helm

Manifest

Select one of the following options (with or without CSI driver) to uninstall Dynatrace Operator.

Without CSI driver

With CSI driver

Helm

Select one of the following options (with or without CSI driver) to uninstall Dynatrace Operator.

Without CSI driver

With CSI driver