Try it free

Update a Managed Cluster

  • How-to guide
  • 5-min read

To update a Managed Cluster, follow the steps below.

For which Managed versions you can skip during an update, see Managed version update logic.

Can I always perform Managed version updates sequentially without skipping a version?

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.

  1. Sign in to Cluster Management Console.
  2. Go to Settings > Automatic update.
  3. Turn on Run Dynatrace cluster updates sequentially without skipping a version.
How can I check my installed Managed version?

To check which Dynatrace Managed version you have currently installed, follow these steps.

  1. Sign in to Cluster Management Console or one of your monitoring environments.

  2. 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.

  1. Sign in to Cluster Management Console and select Deployment status.

  2. 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

Before you begin the Managed Cluster update, verify that the following conditions are met.

  • You have at least 5 GB of available disk space on the partition where Dynatrace Managed is installed. For details, see Storage requirements.
  • You wait 24 hours between Managed Cluster updates to ensure that all post-processing steps are completed before initiating another update.
  • If your Managed Cluster consists of fewer than three nodes, Dynatrace Managed will not be accessible during the update process.

Choose an update approach

There are three different approaches to updating a Managed Cluster. Select the approach that best suits your needs.

Automatic update (recommended)

Semi-automatic update

Manual update

Automatic update (recommended)

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.

  1. Sign in to Cluster Management Console.
  2. Go to Settings > Automatic update.
  3. Ensure that Install Dynatrace cluster updates automatically during the selected maintenance window is turned on.
  4. Define a maintenance window start time. The update will run at the time you specify.

Trigger update manually

You can trigger the update manually at any time outside the defined maintenance window via:

  • Automatic update in the Cluster Management Console
  • Cluster API v1 > Updates > Trigger Upgrade

If you have turned off Install Dynatrace cluster updates automatically during the selected maintenance window, you must always trigger the update manually.

Semi-automatic update

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.

Update notification email example
Managed notification email
Managed notification email

To upload an installation package manually to your Managed Cluster, follow these steps.

  1. Sign in to Cluster Management Console.
  2. Go to Settings > Automatic update.
  3. Select Upload installation package to upload the downloaded package to your cluster.
  4. After the upload, the installation package is distributed automatically to all nodes of the Managed Cluster.
    • If you have turned on automatic updates, the update will start automatically during the defined maintenance window.
    • Alternatively, you can trigger the update manually.

Copy installation packages manually

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

Manual update

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.

  • Run the update script for each node in sequence, one node at a time.
  • Wait until the node update completes before starting an update on the next node.

To manually update a Cluster node, follow the steps below and replace <version> with your Dynatrace Managed version.

  1. Go to the update script in:

    /opt/dynatrace-managed/installer/upgrade
  2. Give the update script executable permissions. Use the Linux chmod command.

    [root@localhost]# chmod +x dynatrace-managed-<version>.sh
  3. Run the update script as a root user.

    [root@localhost]# ./dynatrace-managed-<version>.sh --upgrade
  4. Once the update is successfully completed, move on to the next node and repeat the procedure.

    Successful Cluster node update example
    [root@localhost]# ./dynatrace-managed-<version>.sh --upgrade
    Starting Dynatrace <version> installer ... OK
    Testing connection to Dynatrace Mission Control ... OK
    Verifying system compatibility ... OK
    Verifying disk space ... OK
    Verifying Dynatrace directories ... OK
    Verifying system privileges ... OK
    Verifying system connectivity ... OK
    Stopping Dynatrace ... OK
    Preparing system user for Dynatrace ... OK
    Initializing upgrade ... OK
    Checking user permissions ... OK
    Checking file ownership ... OK
    Downloading Dynatrace OneAgent. This may take a few minutes ... OK
    Upgrading. This may take a few minutes ... OK
    Preparing connectivity settings ... OK
    Setting up cluster configuration. This may take a few minutes ... OK
    Starting Dynatrace. This may take up to half an hour ... OK
    Upgrade completed successfully after 8 minutes 50 seconds.
    Dynatrace binaries are located in directory /opt/dynatrace-managed
    Dynatrace data is located in directory /var/opt/dynatrace-managed
    Dynatrace metrics repository is located in directory /var/opt/dynatrace-managed/cassandra
    Dynatrace Elasticsearch store is located in directory /var/opt/dynatrace-managed/elasticsearch
    Dynatrace server store is located in directory /var/opt/dynatrace-managed/server
    Dynatrace session replay store is located in directory /var/opt/dynatrace-managed/server/replayData
    You can now log into your Dynatrace Server at https://10.10.10.10
    [root@localhost]#