From a4a7a9898bb0eda873ea367c281e580db512ff29 Mon Sep 17 00:00:00 2001
From: vikrammoule-redislabs
 <39086205+vikrammoule-redislabs@users.noreply.github.com>
Date: Thu, 22 Jul 2021 12:47:43 +0530
Subject: [PATCH] Add dynatrace issue RED-54704 to upgrade notes

Dynatrace agent installed on the cluster nodes can hamper the working on Envoy process leading to failure of UI and REST API. Prior upgrading we recommed removing Dynatrace completely or try upgrading to newer versions.
---
 content/rs/release-notes/rs-6-0-may-2020.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/rs/release-notes/rs-6-0-may-2020.md b/content/rs/release-notes/rs-6-0-may-2020.md
index be2f353cb1b..b08da4d1c93 100644
--- a/content/rs/release-notes/rs-6-0-may-2020.md
+++ b/content/rs/release-notes/rs-6-0-may-2020.md
@@ -115,6 +115,7 @@ To use the updated modules with a database, you must [upgrade the module on the
     - If replication is enabled, you must run the BGREWRITEAOF command on all slave shards after the upgrade.
     - If replication is not enabled, you must run the BGREWRITEAOF command on all shards after the upgrade.
 - Starting from RS 5.4.2, to preserve the current Redis major.minor version during database upgrade you must use the keep_redis_version option instead of keep_current_version.
+- Dynatrace agent installed on the cluster nodes can hamper the working on Envoy process leading to failure of UI and REST API. Prior upgrading we recommed removing Dynatrace completely or try upgrading to newer versions. 
 
 ### Redis commands