To update a Managed Cluster, follow the steps below.
For which Managed versions you can skip during an update, see Managed version update logic.
Yes, since Dynatrace Managed version 1.324, you have full control over which versions you update to when using the automatic update functionality. To install each version sequentially, follow these steps.
To check which Dynatrace Managed version you have currently installed, follow these steps.
Sign in to Cluster Management Console or one of your monitoring environments.
Open the User menu.
The Dynatrace Managed version number is displayed in the menu.
Alternatively, check the version in the Cluster Management Console by following these steps.
Sign in to Cluster Management Console and select Deployment status.
On the Cluster nodes tab, select a node to display its overview.
The Dynatrace Managed version number is displayed as the value of Version.
Before you begin the Managed Cluster update, verify that the following conditions are met.
There are three different approaches to updating a Managed Cluster. Select the approach that best suits your needs.
By default, installation packages are downloaded automatically from Mission Control as soon as they're available to your Managed Cluster.
For container deployments (for example, Kubernetes), keep the Docker OneAgent installation package for every OneAgent version that's still in use, because without it the Managed Cluster fails to build the OneAgent image and your pods fail to pull it. For details, see OneAgent image packages on the Managed cluster.
After an installation package is downloaded, a 24-hour waiting period is required before an automatic update can run, so the update is attempted during the first scheduled maintenance window that occurs 24 hours after the download completes. The maintenance window uses the server time of the Managed Cluster. For example, you download an installation package today, and the maintenance window starts at 1:00 AM tomorrow. The 24-hour waiting period is still running at that time, so the update runs in the next maintenance window instead. With a daily window, the update runs a day later. With a window on a single day of the week, the update runs a week later.
Define a suitable maintenance window in which the automatic update should run.
You can trigger the update manually at any time outside the defined maintenance window via:
If you have turned off Install Dynatrace cluster updates automatically during the selected maintenance window, you must always trigger the update manually.
If you have turned off the automatic download of installation packages or there is no connection to Mission Control, you will receive an email notification whenever a new installation package is available. The notification email contains links to download the installation packages. After downloading the installation packages, you need to upload them manually to the Managed Cluster.
If you need strict control over the installation package download, you can opt out from automatic download of installation packages, but you then need to update your license. Contact Dynatrace Support for assistance.

To upload an installation package manually to your Managed Cluster, follow these steps.
You can manually copy an installation package to the following directories on each Cluster node.
For cluster updates to:
/opt/dynatrace-managed/installer/upgrade
For OneAgent, RUM JavaScript, ActiveGate, and Synthetic to:
/var/opt/dynatrace-managed/agents
After uploading the installation packages manually to each Cluster node, you need to run the update script on each node. Since the node that you update isn't operating, it's crucial that you manually update one node at a time.
To manually update a Cluster node, follow the steps below and replace <version> with your Dynatrace Managed version.
Go to the update script in:
/opt/dynatrace-managed/installer/upgrade
Give the update script executable permissions. Use the Linux chmod command.
[root@localhost]# chmod +x dynatrace-managed-<version>.sh
Run the update script as a root user.
[root@localhost]# ./dynatrace-managed-<version>.sh --upgrade
Once the update is successfully completed, move on to the next node and repeat the procedure.
[root@localhost]# ./dynatrace-managed-<version>.sh --upgradeStarting Dynatrace <version> installer ... OKTesting connection to Dynatrace Mission Control ... OKVerifying system compatibility ... OKVerifying disk space ... OKVerifying Dynatrace directories ... OKVerifying system privileges ... OKVerifying system connectivity ... OKStopping Dynatrace ... OKPreparing system user for Dynatrace ... OKInitializing upgrade ... OKChecking user permissions ... OKChecking file ownership ... OKDownloading Dynatrace OneAgent. This may take a few minutes ... OKUpgrading. This may take a few minutes ... OKPreparing connectivity settings ... OKSetting up cluster configuration. This may take a few minutes ... OKStarting Dynatrace. This may take up to half an hour ... OKUpgrade completed successfully after 8 minutes 50 seconds.Dynatrace binaries are located in directory /opt/dynatrace-managedDynatrace data is located in directory /var/opt/dynatrace-managedDynatrace metrics repository is located in directory /var/opt/dynatrace-managed/cassandraDynatrace Elasticsearch store is located in directory /var/opt/dynatrace-managed/elasticsearchDynatrace server store is located in directory /var/opt/dynatrace-managed/serverDynatrace session replay store is located in directory /var/opt/dynatrace-managed/server/replayDataYou can now log into your Dynatrace Server at https://10.10.10.10[root@localhost]#