From b61cfe2fe6e292e41e66f03a0e62484aa27e08e0 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Mon, 17 Apr 2023 08:36:00 +0200
Subject: [PATCH 01/55] upgrade work in progress

---
 .../docs/v1/tech/admin-guide/upgrade-new.adoc | 128 ++++++++++++++++++
 site/docs/v1/tech/admin-guide/upgrade.adoc    |  45 ++++++
 2 files changed, 173 insertions(+)
 create mode 100644 site/docs/v1/tech/admin-guide/upgrade-new.adoc

diff --git a/site/docs/v1/tech/admin-guide/upgrade-new.adoc b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
new file mode 100644
index 0000000000..10ca1b712f
--- /dev/null
+++ b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
@@ -0,0 +1,128 @@
+---
+layout: doc
+title: Upgrade FusionAuth
+description: Learn how to upgrade FusionAuth using our bundles and migration scripts
+navcategory: admin
+---
+
+== Upgrading FusionAuth
+
+This guide will help you upgrade FusionAuth, focusing on self-hosted, RPM/DEB/ZIP-based installations. It covers the reasons to upgrade or not, being aware of upgrade options, and various aspects of the upgrade process.
+
+* <<Reasons to Upgrade>>
+* <<Access to new features and functionality>>
+* <<Receive bug fixes and security patches>>
+* <<Improve performance and efficiency>>
+* <<Maintain compatibility with client libraries>>
+* <<Reasons to Not Upgrade>>
+* <<Stability concerns>>
+* <<Time and resource constraints>>
+* <<Customizations that may break in newer versions>>
+* <<Being Aware of Upgrade Options and Notifications>>
+* <<Subscribe to release notifications>>
+* <<Monitor FusionAuth's official blog or social media channels>>
+* <<Stay informed about the latest releases through FusionAuth's documentation and resources>>
+* <<Thinking About Upgrades>>
+* <<Read the Release Notes>>
+
+
+== Reasons to Upgrade
+
+Upgrading to a newer version of FusionAuth can provide the following benefits:
+
+. Access to new features and improvements
+. Improved performance and stability
+. Critical Security updates and patches
+
+== Reasons Not to Upgrade
+
+You might want to delay upgrading in the following situations:
+
+. Your current version is meeting all your requirements
+. You are in the middle of a project or have tight deadlines
+. You have concerns about compatibility with customizations or third-party integrations
+
+== Being Aware of Upgrade Options
+
+Stay informed about new FusionAuth releases and updates by:
+
+. Monitoring the link:/docs/v1/tech/release-notes[release notes]
+. Subscribing to the FusionAuth newsletter
+. Following FusionAuth on social media platforms
+. Monitoring the FusionAuth GitHub repository
+. Participating in the FusionAuth community forum
+
+== How to Think About Upgrades
+
+Before upgrading FusionAuth, consider the following:
+
+. Read the link:/docs/v1/tech/release-notes[release notes].  Release notes help you understand if an update affects you. They include details on new features, improvements, bug fixes, and potential breaking changes.
+. Test the upgrade in a staging or development environment to identify potential issues
+. Plan for any downtime or maintenance windows required for the upgrade
+. Review custom themes, client libraries, and configuration settings for compatibility with the new version
+. Consider using blue/green deployments or rolling upgrades to minimize downtime
+
+== Upgrading Custom Themes
+
+To upgrade your custom theme, you need to do a diff of theme changes across versions. Consider starting a project that pulls down the default theme from each released version of FusionAuth and commits it to a GitHub repository. You can use the FusionAuth Theme Helper as a starting point.
+
+== Migrating FusionAuth Configuration Changes Between Environments
+
+Refer to the Configuration Management guide for information on migrating configuration changes between environments.
+
+== Upgrading Your Database with Minimal Downtime
+
+Upgrade your database with minimal downtime by following the instructions in the Database section below.
+
+== Switching Out Nodes in a Cluster
+
+If you're running FusionAuth in a cluster, you'll need to switch out nodes one by one during the upgrade. The first node switched out checks for the correct schema and upgrades if needed.
+
+== Handling Main Use Cases
+
+The upgrade process may vary depending on whether you're in a development environment, using Docker or Kubernetes, or running in a cluster.
+
+== Upgrading Versions
+
+If you're upgrading from version 1.37 to 1.43, consider upgrading step-by-step through each minor version to ensure compatibility and reduce potential issues.
+
+== Downtime
+
+Determine if an upgrade will cause downtime by using a staging environment or checking if a database migration is necessary. If a database migration is required, there will likely be downtime. The duration of the downtime depends on your specific architecture.
+
+Differentiate between upgrades affecting admin functionality and those impacting end-user login functionality.
+
+== Upgrading Cloud Instances
+
+For upgrading cloud instances, refer to the relevant section in the cloud installation guide.
+
+== Node Readiness
+
+Determine if a node is ready to serve traffic by checking /api/status. Additional guidance may be needed for Helm charts.
+
+== Silent Mode
+
+Silent mode is used for maintenance mode and provides no prompts. In contrast, non-silent mode displays a GUI asking for database connection information.
+
+Upgrade Options
+Easiest Path
+
+Take everything down.
+Upgrade everything.
+Start everything back up.
+FusionAuth owns the schema, resulting in a full outage.
+Rolling Upgrade
+
+For a three-node cluster:
+
+Upgrade one node at a time behind a load balancer.
+Before adding an upgraded node to the load balancer, ensure node 1 is upgraded.
+Alternatively, upgrade nodes 2 and 3 simultaneously, losing capacity but avoiding schema mismatches.
+You can perform in-place upgrades using dpkg -i or stand up entirely new infrastructure.
+Blue/Green Deployment
+
+For a three-node cluster:
+
+Stand up three new nodes with the new version.
+Add node 4 to the cluster. It will lock the database and own it.
+Nodes 1, 2, and 3 may encounter errors
\ No newline at end of file
diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 2ba029f715..1fc29df2d0 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -11,6 +11,10 @@ In order to upgrade FusionAuth to a later version use the following guides. Belo
 
 Topics covered in this document:
 
+* <<Reasons to Upgrade>>
+* <<Reasons to Not Upgrade>>
+* <<Being Aware of Upgrade Options and Notifications>>
+* <<Thinking About Upgrades>>
 * <<ZIP Packages>>
 * <<Linux Packages>>
 ** <<Troubleshooting Upgrade with RPMs>>
@@ -21,6 +25,47 @@ Topics covered in this document:
 
 If you used the FastPath or other installation methods initially, you may prefer to use that same mode to download the latest version of FusionAuth. If you would like to continue by manually downloading the necessary packages, read on.
 
+== When to Upgrade
+
+=== Reasons to Upgrade
+
+Upgrading to a newer version of FusionAuth can provide the following benefits:
+
+. Access to new features and improvements
+. Improved performance and stability
+. Critical Security updates and patches
+
+=== Reasons Not to Upgrade
+
+You might want to delay upgrading in the following situations:
+
+. Your current version is meeting all your requirements
+. You are in the middle of a project or have tight deadlines
+. You have concerns about compatibility with customizations or third-party integrations
+
+=== Being Aware of Upgrade Options
+
+You can stay informed about new FusionAuth releases and updates by:
+
+. Monitoring the link:/docs/v1/tech/release-notes[release notes]
+. Subscribing to the FusionAuth newsletter
+. Following FusionAuth on social media platforms
+. Monitoring the FusionAuth GitHub repository
+. Participating in the FusionAuth community forum
+
+== How to Think About Upgrades
+
+Before upgrading FusionAuth, consider the following:
+
+. Read the link:/docs/v1/tech/release-notes[release notes].  Release notes help you understand if an update affects you. They include details on new features, improvements, bug fixes, and potential breaking changes.
+. Test the upgrade in a staging or development environment to identify potential issues
+. Plan for any downtime or maintenance windows required for the upgrade. If there are changes to the database schema required, this could require more steps and downtime than a pure application upgrade. 
+. Review custom themes, client libraries, and configuration settings for compatibility with the new version
+. Consider using blue/green deployments or rolling upgrades to minimize downtime
+
+
+
+
 [NOTE]
 ====
 *Readme*

From c07f04617286ed892757c0c1ab6b94284afd67a6 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Tue, 18 Apr 2023 16:27:24 +0200
Subject: [PATCH 02/55] small whitespace edits

---
 site/docs/v1/tech/admin-guide/upgrade-new.adoc | 5 +----
 site/docs/v1/tech/admin-guide/upgrade.adoc     | 2 --
 2 files changed, 1 insertion(+), 6 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade-new.adoc b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
index 10ca1b712f..9011db2711 100644
--- a/site/docs/v1/tech/admin-guide/upgrade-new.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
@@ -10,10 +10,7 @@ navcategory: admin
 This guide will help you upgrade FusionAuth, focusing on self-hosted, RPM/DEB/ZIP-based installations. It covers the reasons to upgrade or not, being aware of upgrade options, and various aspects of the upgrade process.
 
 * <<Reasons to Upgrade>>
-* <<Access to new features and functionality>>
-* <<Receive bug fixes and security patches>>
-* <<Improve performance and efficiency>>
-* <<Maintain compatibility with client libraries>>
+
 * <<Reasons to Not Upgrade>>
 * <<Stability concerns>>
 * <<Time and resource constraints>>
diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 1fc29df2d0..a1e58f05fb 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -64,8 +64,6 @@ Before upgrading FusionAuth, consider the following:
 . Consider using blue/green deployments or rolling upgrades to minimize downtime
 
 
-
-
 [NOTE]
 ====
 *Readme*

From 4c3e8f62239f825ae76fdf1319961ce3caa343c2 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Tue, 18 Apr 2023 16:57:41 +0200
Subject: [PATCH 03/55] added new structure

---
 .../docs/v1/tech/admin-guide/upgrade-new.adoc | 156 ++++++------------
 site/docs/v1/tech/admin-guide/upgrade.adoc    |  27 ++-
 2 files changed, 70 insertions(+), 113 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade-new.adoc b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
index 9011db2711..01c2fe4277 100644
--- a/site/docs/v1/tech/admin-guide/upgrade-new.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
@@ -1,125 +1,61 @@
----
-layout: doc
-title: Upgrade FusionAuth
-description: Learn how to upgrade FusionAuth using our bundles and migration scripts
-navcategory: admin
----
+First:
 
-== Upgrading FusionAuth
+reasons to upgrade
+reasons to not upgrade
+being aware of upgrade options, include release notifications
+Second, how to think about upgrades:
 
-This guide will help you upgrade FusionAuth, focusing on self-hosted, RPM/DEB/ZIP-based installations. It covers the reasons to upgrade or not, being aware of upgrade options, and various aspects of the upgrade process.
+Read the release notes. How do I tell if something affects me?
+How do I upgrade my custom theme (need to document how to do a diff of theme changes across versions, maybe even start a project that does that--pulls down the default theme from each released version of FusionAuth and commits it to a GH repo, perhaps part of this: https://github.com/FusionAuth/fusionauth-theme-helper )
+How do I migrate FusionAuth config changes between environments (pointing to/extracting content from this https://fusionauth.io/docs/v1/tech/admin-guide/configuration-management )
+How can I upgrade my database with minimal downtime?
+How do I switch out nodes if running in a cluster? What happens when the first node is switched out (it checks for the correct schema and upgrades if needed).
+How to handle main use cases: in dev envt, in docker/kubernetes, in cluster.
+Should I upgrade from 1.37 -> 1.43 jumping versions or step by step?
+How can customer know if upgrade will cause downtime? Can they use a staging envrionment to do so? If db migration is shown, yes, otherwise maybe? are there dev team todos to make this clearer? Can we talk about durations for a reference architecture. Differentiate between an upgrade that has downtime around admin functionality and upgrade that affects end user login functionality (the old control plane/data plane metaphor)
+How to upgrade cloud instances (probably just excerpt the section in the cloud install guide)
+How do I know when a node is ready to serve traffic? Helm charts check /, some guidance around checking /api/status. Do we need a new endpoint?
+What is silent mode? It is make maintenance mode work, no prompts, non-silent mode means gui shows up asking for db connection info.
+Third, upgrade options:
 
-* <<Reasons to Upgrade>>
+Easiest path
 
-* <<Reasons to Not Upgrade>>
-* <<Stability concerns>>
-* <<Time and resource constraints>>
-* <<Customizations that may break in newer versions>>
-* <<Being Aware of Upgrade Options and Notifications>>
-* <<Subscribe to release notifications>>
-* <<Monitor FusionAuth's official blog or social media channels>>
-* <<Stay informed about the latest releases through FusionAuth's documentation and resources>>
-* <<Thinking About Upgrades>>
-* <<Read the Release Notes>>
+take everything down, upgrade everything, start it back up,
+fusionatuh owns the schema, full outage
+Rolling upgrade
 
+If you have 3 nodes:
 
-== Reasons to Upgrade
+Upgrade one node at a time behind an LB
 
-Upgrading to a newer version of FusionAuth can provide the following benefits:
+before adding upgraded node load balancer, node 1 upgrades
+or take node 2 and 3 at same time, so lose capacity, not schema mismatch
+Can stand up entirely new infra or run in-place upgrades using dpkg -i
 
-. Access to new features and improvements
-. Improved performance and stability
-. Critical Security updates and patches
+blue/green deployment
 
-== Reasons Not to Upgrade
+Stand up 3 new nodes with new version on it. When adding node 4, it will lock db and own it. nodes 1, 2, 3 may error, may want to remove them. You can add node 4,5,6 at same time as you remove node 1,2,3, or wait for node 4 to complete upgrade. Again, this gets to informing the admin what the impact of an upgrade is.
 
-You might want to delay upgrading in the following situations:
+Out of band DB upgrades
 
-. Your current version is meeting all your requirements
-. You are in the middle of a project or have tight deadlines
-. You have concerns about compatibility with customizations or third-party integrations
+Another option do database updates out of band by yourself. If you have a three node cluster:
 
-== Being Aware of Upgrade Options
+stand up 3 new nodes with new version
+add maintenance page
+take all old version out of service
+run db updates using SQL
+connect three new nodes to the database (maybe need to bounce to get them to reconnect)
+add to load balancer.
+put in diagrams if possible
 
-Stay informed about new FusionAuth releases and updates by:
+faqs
 
-. Monitoring the link:/docs/v1/tech/release-notes[release notes]
-. Subscribing to the FusionAuth newsletter
-. Following FusionAuth on social media platforms
-. Monitoring the FusionAuth GitHub repository
-. Participating in the FusionAuth community forum
+what is runtime mode and how does that affect upgrades
+what is maintenance mode
+what silent mode means
+how many versions can I skip
 
-== How to Think About Upgrades
-
-Before upgrading FusionAuth, consider the following:
-
-. Read the link:/docs/v1/tech/release-notes[release notes].  Release notes help you understand if an update affects you. They include details on new features, improvements, bug fixes, and potential breaking changes.
-. Test the upgrade in a staging or development environment to identify potential issues
-. Plan for any downtime or maintenance windows required for the upgrade
-. Review custom themes, client libraries, and configuration settings for compatibility with the new version
-. Consider using blue/green deployments or rolling upgrades to minimize downtime
-
-== Upgrading Custom Themes
-
-To upgrade your custom theme, you need to do a diff of theme changes across versions. Consider starting a project that pulls down the default theme from each released version of FusionAuth and commits it to a GitHub repository. You can use the FusionAuth Theme Helper as a starting point.
-
-== Migrating FusionAuth Configuration Changes Between Environments
-
-Refer to the Configuration Management guide for information on migrating configuration changes between environments.
-
-== Upgrading Your Database with Minimal Downtime
-
-Upgrade your database with minimal downtime by following the instructions in the Database section below.
-
-== Switching Out Nodes in a Cluster
-
-If you're running FusionAuth in a cluster, you'll need to switch out nodes one by one during the upgrade. The first node switched out checks for the correct schema and upgrades if needed.
-
-== Handling Main Use Cases
-
-The upgrade process may vary depending on whether you're in a development environment, using Docker or Kubernetes, or running in a cluster.
-
-== Upgrading Versions
-
-If you're upgrading from version 1.37 to 1.43, consider upgrading step-by-step through each minor version to ensure compatibility and reduce potential issues.
-
-== Downtime
-
-Determine if an upgrade will cause downtime by using a staging environment or checking if a database migration is necessary. If a database migration is required, there will likely be downtime. The duration of the downtime depends on your specific architecture.
-
-Differentiate between upgrades affecting admin functionality and those impacting end-user login functionality.
-
-== Upgrading Cloud Instances
-
-For upgrading cloud instances, refer to the relevant section in the cloud installation guide.
-
-== Node Readiness
-
-Determine if a node is ready to serve traffic by checking /api/status. Additional guidance may be needed for Helm charts.
-
-== Silent Mode
-
-Silent mode is used for maintenance mode and provides no prompts. In contrast, non-silent mode displays a GUI asking for database connection information.
-
-Upgrade Options
-Easiest Path
-
-Take everything down.
-Upgrade everything.
-Start everything back up.
-FusionAuth owns the schema, resulting in a full outage.
-Rolling Upgrade
-
-For a three-node cluster:
-
-Upgrade one node at a time behind a load balancer.
-Before adding an upgraded node to the load balancer, ensure node 1 is upgraded.
-Alternatively, upgrade nodes 2 and 3 simultaneously, losing capacity but avoiding schema mismatches.
-You can perform in-place upgrades using dpkg -i or stand up entirely new infrastructure.
-Blue/Green Deployment
-
-For a three-node cluster:
-
-Stand up three new nodes with the new version.
-Add node 4 to the cluster. It will lock the database and own it.
-Nodes 1, 2, and 3 may encounter errors
\ No newline at end of file
+we recommended migrating from one minor version to the next over
+how often should I upgrade
+whenever you want. it is your dependency and we won't force you. we recommend staying relatively close to the latest release. in addition, we don't typically backport bug fixes. so if you run into an issue, you'll need to upgrade to get the fix
+how can I find out about new releases
\ No newline at end of file
diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index a1e58f05fb..e5d14d8f94 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -11,9 +11,7 @@ In order to upgrade FusionAuth to a later version use the following guides. Belo
 
 Topics covered in this document:
 
-* <<Reasons to Upgrade>>
-* <<Reasons to Not Upgrade>>
-* <<Being Aware of Upgrade Options and Notifications>>
+* <<When to Upgrade>>
 * <<Thinking About Upgrades>>
 * <<ZIP Packages>>
 * <<Linux Packages>>
@@ -63,6 +61,29 @@ Before upgrading FusionAuth, consider the following:
 . Review custom themes, client libraries, and configuration settings for compatibility with the new version
 . Consider using blue/green deployments or rolling upgrades to minimize downtime
 
+== Upgrade Options
+
+=== Easiest Route
+
+== Rolling Upgrade
+
+=== Blue / Green Deployment
+
+=== Out of Band Database Upgrades
+
+== FAQs
+
+- what is runtime mode and how does that affect upgrades
+- what is maintenance mode
+- what silent mode means
+- how many versions can I skip
+
+- we recommended migrating from one minor version to the next over
+-how often should I upgrade?
+whenever you want. it is your dependency and we won't force you. we recommend staying relatively close to the latest release. in addition, we don't typically backport bug fixes. so if you run into an issue, you'll need to upgrade to get the fix
+- how can I find out about new releases
+
+
 
 [NOTE]
 ====

From 855de288b1175d77a9346cca23b2945bfc736a28 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Fri, 21 Apr 2023 11:24:30 +0200
Subject: [PATCH 04/55] separated old guide to pull in relevant parts to new
 structure

---
 .../docs/v1/tech/admin-guide/upgrade-new.adoc |   2 +
 .../docs/v1/tech/admin-guide/upgrade-old.adoc | 319 ++++++++++++++++++
 2 files changed, 321 insertions(+)
 create mode 100644 site/docs/v1/tech/admin-guide/upgrade-old.adoc

diff --git a/site/docs/v1/tech/admin-guide/upgrade-new.adoc b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
index 01c2fe4277..c44fbdd089 100644
--- a/site/docs/v1/tech/admin-guide/upgrade-new.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
@@ -16,6 +16,8 @@ How can customer know if upgrade will cause downtime? Can they use a staging env
 How to upgrade cloud instances (probably just excerpt the section in the cloud install guide)
 How do I know when a node is ready to serve traffic? Helm charts check /, some guidance around checking /api/status. Do we need a new endpoint?
 What is silent mode? It is make maintenance mode work, no prompts, non-silent mode means gui shows up asking for db connection info.
+
+
 Third, upgrade options:
 
 Easiest path
diff --git a/site/docs/v1/tech/admin-guide/upgrade-old.adoc b/site/docs/v1/tech/admin-guide/upgrade-old.adoc
new file mode 100644
index 0000000000..2ba029f715
--- /dev/null
+++ b/site/docs/v1/tech/admin-guide/upgrade-old.adoc
@@ -0,0 +1,319 @@
+---
+layout: doc
+title: Upgrade FusionAuth
+description: Learn how to upgrade FusionAuth using our bundles and migration scripts
+navcategory: admin
+---
+
+== Upgrading
+
+In order to upgrade FusionAuth to a later version use the following guides. Below you will find steps to follow if you are using `.deb` or `.rpm` package on Linux, or a `.zip` package on macOS, Linux or Windows.
+
+Topics covered in this document:
+
+* <<ZIP Packages>>
+* <<Linux Packages>>
+** <<Troubleshooting Upgrade with RPMs>>
+* <<FastPath>>
+* <<Database>>
+* <<Themes>>
+* <<Downtime>>
+
+If you used the FastPath or other installation methods initially, you may prefer to use that same mode to download the latest version of FusionAuth. If you would like to continue by manually downloading the necessary packages, read on.
+
+[NOTE]
+====
+*Readme*
+
+To upgrade to the latest version of FusionAuth using the FastPath installation go link:/docs/v1/tech/installation-guide/fast-path[here].
+
+To upgrade to the latest version of FusionAuth using Homebrew go link:/docs/v1/tech/installation-guide/homebrew[here].
+
+To upgrade to the latest version of FusionAuth using Docker go link:/docs/v1/tech/installation-guide/docker[here].
+
+If you want to use manual mode, download the latest version of FusionAuth and follow the instructions below. See https://fusionauth.io/download[Downloads].
+====
+
+
+== ZIP Packages
+
+FusionAuth is available in a zip package for macOS, Linux and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth.
+
+=== macOS and Linux
+
+In this example, we'll assume you have previously installed FusionAuth in `/usr/local/fusionauth` and this directory will be referred to `FUSIONAUTH_HOME`. If you have used a different directory you can adjust the following example accordingly.
+
+[source,title=Example filesystem layout]
+----
+/usr/local/fusionauth/bin
+/usr/local/fusionauth/config
+/usr/local/fusionauth/config/keystore
+/usr/local/fusionauth/config/fusionauth.properties
+/usr/local/fusionauth/data
+/usr/local/fusionauth/fusionauth-app
+/usr/local/fusionauth/fusionauth-search
+/usr/local/fusionauth/java
+----
+
+The first step will be to shutdown the FusionAuth services.
+
+[source,title=Shutdown and Uninstall FusionAuth]
+----
+# Stop Services
+/usr/local/fusionauth/bin/shutdown.sh
+
+# Delete or move existing installation
+cd /usr/local/fusionauth
+rm -rf ./fusionauth-app
+rm -rf ./fusionauth-search
+rm -rf ./bin
+----
+
+During an upgrade, most everything is saved in the database, so it is safe to delete these directories. To preserve your configuration and Elasticsearch index you want to be sure to preserve the following directories:
+
+[source,title=Preserve these directories]
+----
+/usr/local/fusionauth/config
+/usr/local/fusionauth/data
+/usr/local/fusionauth/java
+/usr/local/fusionauth/logs
+----
+
+Extract the new zips and place in `FUSIONAUTH_HOME`. In the following example, we are using the `unzip` command with the `-n` and the `-q` flags. The `-q` flag is optional, it causes the command to be run in quiet mode to reduce the amount of output to the console. The other flag `-n` is a no overwrite flag so that any configuration files are not overwritten.
+
+[source,title=Unzip the new packages with a no overwrite flag]
+----
+unzip -nq new-fusionauth-app.zip
+unzip -nq new-fusionauth-search.zip
+----
+
+Finally restart the FusionAuth services.
+
+[source,title=Startup FusionAuth]
+----
+# Start Services
+/usr/local/fusionauth/bin/startup.sh
+----
+
+=== Windows
+
+In this example, we'll assume you have previously installed FusionAuth in `\fusionauth` and this directory will be referred to `FUSIONAUTH_HOME`. If you have used a different directory you can adjust the following example accordingly.
+
+[source,title=Example filesystem layout]
+----
+\fusionauth\bin
+\fusionauth\config
+\fusionauth\config\keystore
+\fusionauth\config\fusionauth.properties
+\fusionauth\data
+\fusionauth\fusionauth-app
+\fusionauth\fusionauth-search
+\fusionauth\java
+----
+
+The first step will be to shutdown the FusionAuth services and delete the old installation.
+
+[source,title=Shutdown and Uninstall FusionAuth]
+----
+# Stop Services
+net stop FusionAuthApp
+net stop FusionAuthSearch
+
+# Uninstall Services
+cd \fusionauth\fusionauth-app\bin
+FusionAuthApp.exe /uninstall
+cd \fusionauth\fusionauth-search\elasticsearch\bin
+FusionAuthSearch.exe /uninstall
+
+# Delete or move existing installation
+cd \fusionauth
+move fusionauth-app fusionauth-app-old
+move fusionauth-search fusionauth-search-old
+----
+
+[NOTE]
+====
+Prior to version `1.37.0` the executable will be found in the `apache-tomcat` directory. For example,
+
+`\fusionauth\fusionauth-app\apache-tomcat\bin\FusionAuthApp.exe`
+
+Versions 1.37.0 through 1.39.0 do not support native Windows installation.
+====
+
+During an upgrade, most everything is saved in the database, so it is safe to delete these directories. To preserve your configuration and Elasticsearch index you want to be sure to preserve the following directories:
+
+[source,title=Preserve these directories]
+----
+\fusionauth\config
+\fusionauth\data
+\fusionauth\java
+\fusionauth\logs
+----
+
+Extract the new zips and place in `FUSIONAUTH_HOME`. You may do this using Windows File Explorer or other command line tools to unpack the zip archive. In this next step, ensure you delete or move the existing directories to ensure you do not unzip the new version on top of the existing version. If you do this, you will end up with duplicate libraries in the classpath that will lead to runtime errors.
+
+After you have extracted the new packages, re-install the Windows services and start them.
+
+[source,title=Install and Start FusionAuth]
+----
+# Install Windows Services
+cd \fusionauth\fusionauth-app\bin
+FusionAuthApp.exe /install
+cd \fusionauth\fusionauth-search\elasticsearch\bin
+FusionAuthSearch.exe /install
+
+# Startup Services
+net start FusionAuthSearch
+net start FusionAuthApp
+----
+
+[NOTE]
+====
+Prior to version 1.37.0 you can find `FusionAuthApp.exe` at
+
+`\fusionauth\fusionauth-app\apache-tomcat\bin\FusionAuthApp.exe`
+
+Versions 1.37.0 through 1.39.0 do not support native Windows installation.
+====
+
+That is it, you're done!
+
+== Linux Packages
+
+Updating your application is easy if you installed using the RPM or Debian packages. All you need to do is to issue an update command to the dpkg or rpm program and specify the new package file. Here is an example:
+
+[NOTE]
+====
+Running the update script will shut down the FusionAuth service if they have not yet been stopped The service will need to be restarted after the update is finished.
+====
+
+[source,title=Shutdown FusionAuth]
+----
+sudo service fusionauth-app stop
+sudo service fusionauth-search stop
+----
+
+[source,shell,title=Upgrade FusionAuth using Debian bundles]
+----
+sudo dpkg -i fusionauth-search-<version>.deb
+sudo dpkg -i fusionauth-app-<version>.deb
+----
+
+[source,shell,title=Upgrade FusionAuth using RPM bundles]
+----
+sudo rpm -U fusionauth-search-<version>.rpm
+sudo rpm -U fusionauth-app-<version>.rpm
+----
+
+[source,title=Start FusionAuth]
+----
+sudo systemctl start fusionauth-search
+sudo systemctl start fusionauth-app
+----
+
+=== Troubleshooting Upgrade with RPMs
+
+include::docs/v1/tech/shared/_troubleshooting-uninstall-upgrade-reinstall-rpm.adoc[]
+
+=== FastPath
+
+While FastPath is an option to perform an upgrade, the FastPath process limits the flexibility of installation in order to get up and running quickly. Therefore it is not recommended to use FastPath install scripts in a Production Environment.
+
+When in a production environment please utilize `.deb` or `.rpm` packages when on Linux. If you your production platform is macOS or Windows, please manually manage the upgrade using the `.zip` bundles.
+
+== Database
+
+[NOTE]
+====
+If you want FusionAuth to upgrade the database automatically, use the link:/docs/v1/tech/guides/silent-mode[Silent Mode] process, which will perform an automated upgrade.
+
+If you want to use Maintenance Mode, ensure your runtime mode is set to `development` and silent mode is set to `false`.
+
+If you want to upgrade the database manually, follow the instructions below.
+
+For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide] for reference.
+
+For more information on the various configuration options, see the link:/docs/v1/tech/reference/configuration[Configuration Reference].
+====
+
+[NOTE]
+====
+You should always backup your database prior to using Maintenance Mode.
+====
+
+Depending on your current version and the new version you will be updating to you might need to execute one or more SQL scripts to update your
+ database. These scripts are located in the migrations folder inside the Database Schema ZIP file. This file can be downloaded by finding the database zip on the https://fusionauth.io/direct-download[Direct Downloads] page.
+
+[WARNING]
+====
+When upgrading your database from a previous version, be sure to only run the scripts located in the `migrations` folder, the base files
+ `mysql.sql` and `postgresql.sql` should only be used during a clean installation when no database schema is present.
+====
+
+Inside of the database schema zip file, you will find the FusionAuth migrations. Run them in order, starting with the first migration greater than the version you are coming from, and ending with the version that is less than or equal to the target upgrade version.
+
+For example, if upgrading from version `1.19.1` to `1.22.0`, run the following SQL migrations in this order:
+
+* `1.20.0.sql`
+* `1.21.0.sql`
+* `1.22.0.sql`
+
+[source]
+----
+fusionauth-database-schema/
+|-- migrations/
+    |--  [mysql | postgresql]/
+      |-- 1.1.0.sql
+      |-- 1.2.0.sql
+      |-- 1.3.0.sql
+      |-- 1.3.1.sql
+      |-- 1.5.0.sql
+      |-- 1.6.0.sql
+      |-- 1.7.0.sql
+      |-- 1.7.1.sql
+      |-- 1.8.0-RC.1.sql
+      |-- 1.8.1-RC.1.sql
+      |-- 1.11.0.sql
+      |-- 1.12.0.sql
+      |-- 1.13.0.sql
+      |-- 1.14.0.sql
+      |-- 1.15.0.sql
+      |-- 1.15.3.sql
+      |-- 1.16.0-RC.1.sql
+      |-- 1.16.0.sql
+      |-- 1.17.0.sql
+      |-- 1.17.3.sql
+      |-- 1.18.0.sql
+      |-- 1.18.2.sql
+      |-- 1.19.0.sql
+      |-- 1.20.0.sql
+      |-- 1.21.0.sql
+      |-- 1.22.0.sql
+      |-- 1.23.0.sql
+      |-- 1.25.0.sql
+      |-- 1.26.0.sql
+      |-- 1.27.0.sql
+      |-- 1.28.0.sql
+      |-- 1.28.1.sql
+      |-- 1.29.1.sql
+      |-- 1.30.0.sql
+      |-- 1.30.1.sql
+      |-- 1.30.2.sql
+      |-- 1.32.0.sql
+      |-- 1.33.0.sql
+      |-- 1.35.0.sql
+      |-- 1.36.0.sql
+      |-- 1.37.0.sql
+      |-- 1.40.1.sql
+      |-- 1.41.0.sql
+      |-- 1.43.0.sql
+      |-- 1.44.0.sql
+----
+
+== Themes
+
+include::docs/v1/tech/installation-guide/_theme-upgrade.adoc[]
+
+== Downtime
+
+include::docs/v1/tech/installation-guide/_downtime-upgrade-limitation.adoc[]

From 4e26ff842c56270aa34764c41f2179e9a11c5854 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Wed, 26 Apr 2023 09:55:48 +0200
Subject: [PATCH 05/55] structuring

---
 .../docs/v1/tech/admin-guide/upgrade-new.adoc |  7 +++++-
 site/docs/v1/tech/admin-guide/upgrade.adoc    | 23 ++++++++++++-------
 2 files changed, 21 insertions(+), 9 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade-new.adoc b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
index c44fbdd089..0eefe108fc 100644
--- a/site/docs/v1/tech/admin-guide/upgrade-new.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
@@ -12,9 +12,14 @@ How can I upgrade my database with minimal downtime?
 How do I switch out nodes if running in a cluster? What happens when the first node is switched out (it checks for the correct schema and upgrades if needed).
 How to handle main use cases: in dev envt, in docker/kubernetes, in cluster.
 Should I upgrade from 1.37 -> 1.43 jumping versions or step by step?
-How can customer know if upgrade will cause downtime? Can they use a staging envrionment to do so? If db migration is shown, yes, otherwise maybe? are there dev team todos to make this clearer? Can we talk about durations for a reference architecture. Differentiate between an upgrade that has downtime around admin functionality and upgrade that affects end user login functionality (the old control plane/data plane metaphor)
+How can customer know if upgrade will cause downtime? Can they use a staging envrionment to do so? If db migration is shown, yes, otherwise maybe? are there dev team todos to make this clearer? Can we talk about durations for a reference architecture. 
+
+Differentiate between an upgrade that has downtime around admin functionality and upgrade that affects end user login functionality (the old control plane/data plane metaphor)
+
 How to upgrade cloud instances (probably just excerpt the section in the cloud install guide)
+
 How do I know when a node is ready to serve traffic? Helm charts check /, some guidance around checking /api/status. Do we need a new endpoint?
+
 What is silent mode? It is make maintenance mode work, no prompts, non-silent mode means gui shows up asking for db connection info.
 
 
diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index e5d14d8f94..fdbdbe03a7 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -65,23 +65,30 @@ Before upgrading FusionAuth, consider the following:
 
 === Easiest Route
 
+The easiest route with the least pre-planning and logistics is to simply stop all your services, upgrade everything, and then bring it all back online. 
+
+The disadvantage of this is that your site will experience a full outage. This may be acceptable for many use cases eg. internal systems that are only used during office hours, or a website that is only used during certain hours in a particular timezone. 
+
+If downtime is not an option then rolling upgrades, or a blue/green deployment might be more suitable. 
+
 == Rolling Upgrade
 
+
 === Blue / Green Deployment
 
 === Out of Band Database Upgrades
 
 == FAQs
 
-- what is runtime mode and how does that affect upgrades
-- what is maintenance mode
-- what silent mode means
-- how many versions can I skip
+Q: What is runtime mode and how does that affect upgrades
+Q: What is maintenance mode
+Q: What silent mode means
+Q: How many versions can I skip?
+A: We recommended migrating from one minor version to the next over
 
-- we recommended migrating from one minor version to the next over
--how often should I upgrade?
-whenever you want. it is your dependency and we won't force you. we recommend staying relatively close to the latest release. in addition, we don't typically backport bug fixes. so if you run into an issue, you'll need to upgrade to get the fix
-- how can I find out about new releases
+Q: How often should I upgrade?
+A: You can upgrade whenever you want. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release. In addition, we don't typically backport bug fixes. so if you run into an issue, you'll need to upgrade to get the fix
+Q: How can I find out about new releases
 
 
 

From 7926212c9cbc9a80cd4df90b242c6e4a0cec4528 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Mon, 8 May 2023 12:51:20 +0200
Subject: [PATCH 06/55] red /green, thinking about upgrades

---
 .../docs/admin-guide/upgrade/blue-green.svg   | 16 +++++
 .../admin-guide/upgrade/rolling-upgrade.svg   | 16 +++++
 site/docs/v1/tech/admin-guide/upgrade.adoc    | 61 ++++++++++++++-----
 3 files changed, 77 insertions(+), 16 deletions(-)
 create mode 100644 site/assets/img/docs/admin-guide/upgrade/blue-green.svg
 create mode 100644 site/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg

diff --git a/site/assets/img/docs/admin-guide/upgrade/blue-green.svg b/site/assets/img/docs/admin-guide/upgrade/blue-green.svg
new file mode 100644
index 0000000000..5acb31122a
--- /dev/null
+++ b/site/assets/img/docs/admin-guide/upgrade/blue-green.svg
@@ -0,0 +1,16 @@
+<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 809.0030546609328 708.1438392940221" width="1618.0061093218656" height="1416.2876785880442">
+  <!-- svg-source:excalidraw -->
+  
+  <defs>
+    <style class="style-fonts">
+      @font-face {
+        font-family: "Virgil";
+        src: url("https://excalidraw.com/Virgil.woff2");
+      }
+      @font-face {
+        font-family: "Cascadia";
+        src: url("https://excalidraw.com/Cascadia.woff2");
+      }
+    </style>
+  </defs>
+  <rect x="0" y="0" width="809.0030546609328" height="708.1438392940221" fill="#ffffff"></rect><g stroke-linecap="round" transform="translate(537.3571990951166 10) rotate(0 98.99999999999994 140)"><path d="M7.86 8.16 C7.86 8.16, 7.86 8.16, 7.86 8.16 M7.86 8.16 C7.86 8.16, 7.86 8.16, 7.86 8.16 M3.66 19.09 C9.47 15.42, 11.56 10.75, 18.1 2.48 M3.66 19.09 C7.67 14.35, 12.6 9.92, 18.1 2.48 M2.75 26.24 C8.27 18.95, 13.86 13.92, 24.4 1.33 M2.75 26.24 C7.98 19.35, 15.42 13.47, 24.4 1.33 M2.48 32.64 C10.8 23.54, 16.31 17.58, 30.7 0.18 M2.48 32.64 C12.91 20.39, 24.86 8.19, 30.7 0.18 M2.88 38.28 C13.92 23.64, 24.57 9.31, 34.37 2.05 M2.88 38.28 C15.2 26.07, 25.44 12.1, 34.37 2.05 M2.62 44.68 C11.97 34.46, 18.94 25.51, 39.36 2.41 M2.62 44.68 C15.65 29.87, 26.87 15.62, 39.36 2.41 M2.36 51.07 C19.07 32.93, 31.56 18.67, 45 2.02 M2.36 51.07 C14 39.3, 24.8 26.01, 45 2.02 M2.75 56.72 C11.42 47.44, 20.8 33.53, 49.99 2.38 M2.75 56.72 C16.6 39.35, 31.88 24.3, 49.99 2.38 M2.49 63.11 C18.61 45.76, 30.37 30.88, 55.63 1.98 M2.49 63.11 C22 40.75, 41.01 19.52, 55.63 1.98 M2.23 69.51 C23.23 48.05, 43.28 25.07, 60.62 2.34 M2.23 69.51 C17.16 51.98, 31.95 33.38, 60.62 2.34 M2.62 75.16 C18.43 57.29, 35.53 38.31, 66.26 1.95 M2.62 75.16 C16.38 60.45, 29.44 44.41, 66.26 1.95 M2.36 81.55 C30.39 52.12, 54.61 19.73, 71.25 2.31 M2.36 81.55 C18.61 63.81, 32.64 45.17, 71.25 2.31 M2.76 87.2 C24.53 60.86, 47.27 34.66, 76.89 1.91 M2.76 87.2 C18.27 68.75, 34.36 51.22, 76.89 1.91 M2.49 93.59 C21.52 72.87, 37.01 53.28, 81.88 2.27 M2.49 93.59 C29.9 63.21, 55.4 32.58, 81.88 2.27 M2.23 99.99 C31.92 64.72, 62.47 29.53, 87.52 1.88 M2.23 99.99 C31.12 66.97, 58.71 34.03, 87.52 1.88 M2.63 105.64 C30.33 73.56, 60 42.84, 92.51 2.24 M2.63 105.64 C31.23 73.35, 59.23 41.6, 92.51 2.24 M2.37 112.03 C21.63 91.55, 39.19 70.07, 97.49 2.6 M2.37 112.03 C20.67 89.69, 41.31 67.9, 97.49 2.6 M2.76 117.68 C33.89 81.93, 67.48 44.03, 103.14 2.21 M2.76 117.68 C44.79 69.72, 83.25 24.43, 103.14 2.21 M2.5 124.07 C30.25 93.76, 55.54 64.67, 108.12 2.57 M2.5 124.07 C43.9 76.2, 85.4 28.41, 108.12 2.57 M2.24 130.47 C23.94 103.44, 46.04 74.99, 113.77 2.17 M2.24 130.47 C28.59 99.78, 53.47 68.5, 113.77 2.17 M2.63 136.11 C40.84 91.94, 80.28 48.75, 118.76 2.53 M2.63 136.11 C43.28 90.67, 83.01 43.07, 118.76 2.53 M2.37 142.51 C48.32 88.64, 94.74 35.13, 124.4 2.14 M2.37 142.51 C49.6 89.23, 96.32 35.77, 124.4 2.14 M2.11 148.91 C37.12 108.39, 67.72 68.06, 129.39 2.5 M2.11 148.91 C34.23 109.56, 66.43 71.5, 129.39 2.5 M2.5 154.55 C48.3 100.9, 97.04 44.83, 135.03 2.1 M2.5 154.55 C29.7 123.05, 55.87 92.84, 135.03 2.1 M2.24 160.95 C52.21 106.29, 96.79 53.76, 140.02 2.46 M2.24 160.95 C55.53 99.2, 107.57 38.59, 140.02 2.46 M2.64 166.59 C37.37 128.24, 71.93 87.58, 145 2.82 M2.64 166.59 C53.03 107.09, 106.16 47.3, 145 2.82 M2.38 172.99 C33.38 138.8, 64.68 102.65, 150.65 2.43 M2.38 172.99 C51.92 117.41, 100.63 60.79, 150.65 2.43 M2.11 179.39 C48.77 125.78, 95.67 72.45, 155.63 2.79 M2.11 179.39 C55.53 120.01, 108.86 59.42, 155.63 2.79 M2.51 185.03 C61.39 117.14, 122.22 47.51, 161.28 2.39 M2.51 185.03 C61.79 117.77, 120.28 50.41, 161.28 2.39 M2.25 191.43 C66.49 117.79, 133.59 40.57, 166.26 2.75 M2.25 191.43 C55.66 130.45, 110.13 67.15, 166.26 2.75 M1.99 197.83 C60.02 132.39, 116.72 66.48, 173.22 0.85 M1.99 197.83 C56.53 132.65, 113.37 68.68, 173.22 0.85 M2.38 203.47 C55.8 142.54, 105.92 83.19, 177.55 1.96 M2.38 203.47 C59.82 141.49, 114.71 77.48, 177.55 1.96 M2.12 209.87 C43.53 162.4, 83.98 115.33, 181.88 3.08 M2.12 209.87 C56.68 149.81, 109.58 89.9, 181.88 3.08 M2.51 215.51 C41.77 170.26, 80.94 125.02, 185.55 4.95 M2.51 215.51 C39.85 172.79, 76.08 130.15, 185.55 4.95 M2.25 221.91 C70.63 142.11, 143.67 61.15, 188.57 7.57 M2.25 221.91 C60.76 155.88, 116.82 90.54, 188.57 7.57 M1.99 228.31 C48.27 175.49, 96.07 122.47, 191.59 10.2 M1.99 228.31 C58.61 163.46, 114.14 97.56, 191.59 10.2 M2.39 233.95 C75.53 151.15, 147.62 67.13, 194.61 12.82 M2.39 233.95 C53.67 174.26, 105.92 114.26, 194.61 12.82 M2.12 240.35 C68.62 165.51, 132.83 89.47, 196.32 16.95 M2.12 240.35 C46.63 191.53, 88.52 142.77, 196.32 16.95 M0.55 248.26 C75.78 163.4, 147.54 79.95, 198.68 20.33 M0.55 248.26 C47.69 193.69, 95.01 139.72, 198.68 20.33 M0.95 253.9 C68.72 178.23, 132.79 100.65, 199.73 25.22 M0.95 253.9 C80.67 163.74, 158.9 73.2, 199.73 25.22 M2 258.79 C76.1 172.49, 151.96 88.25, 198.81 32.37 M2 258.79 C67.85 183.56, 133.5 109.2, 198.81 32.37 M3.7 262.92 C62.42 193.75, 120.04 126.32, 198.55 38.77 M3.7 262.92 C72.98 184.17, 142.28 105.82, 198.55 38.77 M4.75 267.81 C79.93 180.18, 157.01 94.35, 198.95 44.42 M4.75 267.81 C48.64 217, 92.09 167.99, 198.95 44.42 M7.77 270.43 C50.97 221.78, 90.05 172.25, 198.69 50.81 M7.77 270.43 C54.51 218.41, 100.56 165.1, 198.69 50.81 M10.79 273.06 C60.58 216.82, 108.64 159.24, 198.42 57.21 M10.79 273.06 C55.68 218.89, 101.59 166.54, 198.42 57.21 M13.15 276.44 C69.83 214.75, 121.13 153.32, 198.82 62.85 M13.15 276.44 C68.52 212.96, 124.02 148.41, 198.82 62.85 M16.83 278.31 C54.21 235.36, 93.99 192.29, 198.56 69.25 M16.83 278.31 C67.38 218.94, 118.87 159.68, 198.56 69.25 M20.5 280.18 C62.42 232.72, 101.83 185.59, 198.95 74.89 M20.5 280.18 C89.12 200.94, 158.21 120.72, 198.95 74.89 M25.49 280.54 C80.64 213.24, 139.59 149.3, 198.69 81.29 M25.49 280.54 C76.88 221.62, 126.47 163.02, 198.69 81.29 M29.82 281.65 C93.6 204.65, 157.41 130.78, 198.43 87.69 M29.82 281.65 C77.25 228.07, 122.07 176.52, 198.43 87.69 M34.81 282.01 C77.48 232.92, 124.56 182.3, 198.82 93.33 M34.81 282.01 C96.14 213.6, 156.81 141.99, 198.82 93.33 M39.8 282.37 C102.68 208.38, 163.45 135.29, 198.56 99.73 M39.8 282.37 C90.08 224.02, 139.95 165.67, 198.56 99.73 M45.44 281.98 C99.27 218.78, 155.89 157.15, 198.96 105.37 M45.44 281.98 C90.26 230.04, 133.6 179.62, 198.96 105.37 M50.43 282.34 C100.82 222.99, 151.22 168.21, 198.69 111.77 M50.43 282.34 C80.02 245.85, 111.67 209.55, 198.69 111.77 M56.07 281.94 C97.47 232.53, 136.67 186.79, 198.43 118.17 M56.07 281.94 C107.75 222.22, 159.41 164.4, 198.43 118.17 M61.06 282.3 C112.44 222.23, 168.44 161.3, 198.83 123.81 M61.06 282.3 C94.26 245.15, 127.9 208.51, 198.83 123.81 M66.7 281.91 C93.15 250.33, 121 216.01, 198.57 130.21 M66.7 281.91 C115.93 226.14, 164.21 169.97, 198.57 130.21 M71.69 282.27 C114.27 230.43, 160.61 180.29, 198.96 135.85 M71.69 282.27 C121.02 224.06, 171.25 166.19, 198.96 135.85 M76.67 282.63 C107.03 247.99, 136.46 214.26, 198.7 142.25 M76.67 282.63 C106.53 246.7, 135.96 211.51, 198.7 142.25 M82.32 282.23 C123.89 232.95, 164.74 186.67, 198.44 148.65 M82.32 282.23 C114.69 246.04, 146.88 208.78, 198.44 148.65 M87.3 282.59 C109.54 259.35, 131.46 232.95, 198.83 154.29 M87.3 282.59 C131.7 230.13, 175.37 180.62, 198.83 154.29 M92.95 282.2 C127.75 238.63, 163.41 197.42, 198.57 160.69 M92.95 282.2 C115.01 257.21, 136.64 232.85, 198.57 160.69 M97.93 282.56 C120.02 257.39, 144.93 229.1, 198.97 166.33 M97.93 282.56 C134.92 240.37, 171.84 197.9, 198.97 166.33 M103.58 282.16 C137.81 241.12, 172.4 204.23, 198.7 172.73 M103.58 282.16 C131.83 249.39, 158.7 217.07, 198.7 172.73 M108.56 282.52 C137.86 248.42, 171.73 212.34, 198.44 179.13 M108.56 282.52 C140.01 244.82, 173.52 207.35, 198.44 179.13 M114.21 282.13 C135.24 254.26, 158.12 228.24, 198.84 184.77 M114.21 282.13 C146.15 247.55, 177.42 210.63, 198.84 184.77 M119.19 282.49 C148.23 251.61, 176.42 216.04, 198.58 191.17 M119.19 282.49 C147.52 250.02, 174.3 217.27, 198.58 191.17 M124.84 282.1 C147.03 259.35, 168.7 233.8, 198.97 196.81 M124.84 282.1 C144.77 259.42, 163.34 235.95, 198.97 196.81 M129.82 282.46 C151.22 257.84, 176.15 231.68, 198.71 203.21 M129.82 282.46 C155.28 252.85, 180.49 224.42, 198.71 203.21 M135.47 282.06 C149.27 268.79, 159.88 254.7, 198.45 209.61 M135.47 282.06 C156.33 258.52, 176.36 235.81, 198.45 209.61 M140.45 282.42 C157.34 264.11, 173.14 246.81, 198.84 215.25 M140.45 282.42 C163.96 256.11, 186.44 230.79, 198.84 215.25 M146.1 282.03 C164.16 262.4, 180.47 239.84, 198.58 221.65 M146.1 282.03 C162.25 264.45, 176.53 246.52, 198.58 221.65 M151.08 282.39 C163.86 268.72, 177.41 252.92, 198.98 227.29 M151.08 282.39 C163.42 267.88, 176.06 254.24, 198.98 227.29 M156.73 281.99 C169.04 269.04, 178.3 258.29, 198.71 233.69 M156.73 281.99 C166.15 270.65, 177.54 259.33, 198.71 233.69 M161.71 282.35 C171.43 272.88, 176.57 264.21, 198.45 240.09 M161.71 282.35 C175.74 266.05, 189.27 250.48, 198.45 240.09 M168.01 281.2 C180.76 268.15, 191.89 255.35, 198.85 245.73 M168.01 281.2 C174.73 273.43, 182.52 266.32, 198.85 245.73 M173.66 280.81 C178.85 272.79, 184.87 267.23, 200.55 249.86 M173.66 280.81 C185.08 267.62, 194.82 257.02, 200.55 249.86 M180.61 278.9 C189.51 268.48, 196.58 263.47, 199.64 257.02 M180.61 278.9 C185.55 274.24, 189.42 269.41, 199.64 257.02" stroke="#4c6ef5" stroke-width="0.5" fill="none"></path><path d="M32 0 M32 0 C60.97 -3.14, 90.58 -2.55, 166 0 M32 0 C76.83 1.29, 120.82 1.12, 166 0 M166 0 C187.41 0.97, 197.42 10.16, 198 32 M166 0 C188.97 0.1, 199.17 12.86, 198 32 M198 32 C199.24 103.34, 198.47 174.44, 198 248 M198 32 C198.88 116.47, 199.05 201.51, 198 248 M198 248 C199.14 267.7, 185.59 278.1, 166 280 M198 248 C199.11 271.41, 187.81 280.49, 166 280 M166 280 C127.86 279.76, 89.29 281.35, 32 280 M166 280 C126.54 279.31, 85.04 278.49, 32 280 M32 280 C12.35 281.02, 1.87 267.66, 0 248 M32 280 C9.78 277.91, -0.05 271.06, 0 248 M0 248 C-0.3 177.86, 0.8 105.38, 0 32 M0 248 C-1.07 195.89, 0.46 144.56, 0 32 M0 32 C0.35 9.97, 11.54 0.35, 32 0 M0 32 C-0.3 12.12, 9.54 1.3, 32 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g stroke-linecap="round" transform="translate(557.3571990951166 41.306603130202745) rotate(0 78 23)"><path d="M10.72 -1 L148.98 -0.45 L154.2 2.18 L157.02 6.91 L153.74 39.99 L151.8 45.27 L144.82 44.85 L8.07 45.69 L4.86 45.12 L1.56 37.22 L-0.7 7.41 L4.09 2.13 L13.21 0.53" stroke="none" stroke-width="0" fill="#228be6"></path><path d="M11.5 0 M11.5 0 C38.91 -2.04, 64.2 -1.05, 144.5 0 M11.5 0 C47.63 2.2, 84.09 1.31, 144.5 0 M144.5 0 C153 0.75, 154.41 3.62, 156 11.5 M144.5 0 C150.81 1.63, 154.8 3.13, 156 11.5 M156 11.5 C155.72 19.13, 156.84 22.74, 156 34.5 M156 11.5 C156.94 19.51, 155.89 28.32, 156 34.5 M156 34.5 C154.5 42.84, 152.74 45.23, 144.5 46 M156 34.5 C157.69 40.71, 151.89 44.01, 144.5 46 M144.5 46 C101.92 45.42, 61.9 47.03, 11.5 46 M144.5 46 C102.31 45.83, 60.12 46.64, 11.5 46 M11.5 46 C1.84 47.89, -1.2 43.4, 0 34.5 M11.5 46 C4.84 45.69, 1.52 39.9, 0 34.5 M0 34.5 C0.39 28.88, 0.88 21.37, 0 11.5 M0 34.5 C0.27 28.87, -0.42 23.44, 0 11.5 M0 11.5 C-1.95 5.83, 5.53 -1.75, 11.5 0 M0 11.5 C-1.7 3.61, 2.56 -1.11, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(604.5072006209955 51.806603130202745) rotate(0 30.849998474121094 12.5)"><text x="30.849998474121094" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 1</text></g><g stroke-linecap="round" transform="translate(557.3571990951166 106) rotate(0 78 23)"><path d="M10.89 -0.49 L150.3 0.95 L152.76 4.18 L156.57 7.38 L156.56 40.49 L149.96 46.05 L143.77 45.57 L6.61 43.79 L3.54 43.7 L-0.59 38.66 L-1.09 8.57 L1.15 3.13 L10.34 -0.74" stroke="none" stroke-width="0" fill="#228be6"></path><path d="M11.5 0 M11.5 0 C46.29 -0.08, 76.88 -0.77, 144.5 0 M11.5 0 C48.26 -0.18, 84.15 0.21, 144.5 0 M144.5 0 C153.4 0.88, 155.73 5.16, 156 11.5 M144.5 0 C149.9 -0.17, 157.4 1.68, 156 11.5 M156 11.5 C156.45 18.25, 155.32 25.47, 156 34.5 M156 11.5 C157.08 17.84, 157.09 26.98, 156 34.5 M156 34.5 C154.25 40.69, 151.97 44.89, 144.5 46 M156 34.5 C154.89 40.17, 153.7 44.26, 144.5 46 M144.5 46 C98.1 46.34, 52.49 46.04, 11.5 46 M144.5 46 C117.35 45.72, 88.24 45.16, 11.5 46 M11.5 46 C2.28 45.03, -1.25 43.37, 0 34.5 M11.5 46 C4.74 47.46, 0.49 39.94, 0 34.5 M0 34.5 C-0.84 27.71, -0.81 23.46, 0 11.5 M0 34.5 C-0.02 28.06, 0.85 20.71, 0 11.5 M0 11.5 C-0.69 5.5, 4.19 -0.09, 11.5 0 M0 11.5 C-0.65 3.68, 2.79 0.18, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(600.0972007735834 116.5) rotate(0 35.2599983215332 12.5)"><text x="35.2599983215332" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 2</text></g><g stroke-linecap="round" transform="translate(559.3571990951166 184) rotate(0 78 23)"><path d="M12.38 -0.27 L150.86 -1.25 L152.97 4.09 L153.95 9.34 L156.39 40.55 L151.83 43.62 L143.7 44.95 L6.83 46.07 L1.86 45.11 L-1.77 39.19 L1.87 7.05 L1.39 2.68 L10.39 -0.97" stroke="none" stroke-width="0" fill="#4c6ef5"></path><path d="M11.5 0 M11.5 0 C40.64 0.12, 70.07 -0.26, 144.5 0 M11.5 0 C44.52 0.16, 78.4 1.67, 144.5 0 M144.5 0 C154.05 -0.41, 156.75 2.28, 156 11.5 M144.5 0 C151.05 -1.44, 157.38 4.74, 156 11.5 M156 11.5 C154.86 20.42, 154.06 27.44, 156 34.5 M156 11.5 C155.89 17.42, 155.91 22.49, 156 34.5 M156 34.5 C156.78 44.08, 151.92 45.31, 144.5 46 M156 34.5 C157.91 42.57, 152.07 45.35, 144.5 46 M144.5 46 C107.19 46.1, 65.61 46.61, 11.5 46 M144.5 46 C101.42 47.6, 59.59 47.94, 11.5 46 M11.5 46 C3.24 44.34, -1.77 41.33, 0 34.5 M11.5 46 C5.83 48.23, 1.22 41.43, 0 34.5 M0 34.5 C0.27 29.09, -0.74 22.11, 0 11.5 M0 34.5 C0.45 25.61, 0.79 16.48, 0 11.5 M0 11.5 C-0.69 3.83, 4.71 -1.26, 11.5 0 M0 11.5 C-2.25 6.05, 2.09 -1.45, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(602.4071983321771 194.5) rotate(0 34.95000076293945 12.5)"><text x="34.95000076293945" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 3</text></g><g stroke-linecap="round" transform="translate(544.8525020588318 375.10610387388687) rotate(0 98.99999999999994 140)"><path d="M7.86 8.16 C7.86 8.16, 7.86 8.16, 7.86 8.16 M7.86 8.16 C7.86 8.16, 7.86 8.16, 7.86 8.16 M3.66 19.09 C7.37 14.35, 11.74 5.67, 18.1 2.48 M3.66 19.09 C6.85 15.7, 12.15 10.87, 18.1 2.48 M2.75 26.24 C10.93 19.97, 17.03 11.58, 24.4 1.33 M2.75 26.24 C8.9 19.35, 15.84 12.02, 24.4 1.33 M2.48 32.64 C13.67 21.65, 23.31 10.05, 30.7 0.18 M2.48 32.64 C9.72 25.66, 16 17.56, 30.7 0.18 M2.88 38.28 C9.84 25.71, 21.38 18.04, 34.37 2.05 M2.88 38.28 C14.24 26.03, 25.12 11.81, 34.37 2.05 M2.62 44.68 C14.06 29.3, 27.86 16.43, 39.36 2.41 M2.62 44.68 C17.78 28.7, 32.67 10.98, 39.36 2.41 M2.36 51.07 C9.93 39.22, 20.43 27.56, 45 2.02 M2.36 51.07 C11.76 40.62, 20.55 31.42, 45 2.02 M2.75 56.72 C13.72 42.46, 27.89 25.38, 49.99 2.38 M2.75 56.72 C14.13 45.17, 25.39 31.34, 49.99 2.38 M2.49 63.11 C19.26 44.97, 35.8 22.97, 55.63 1.98 M2.49 63.11 C19.31 43.38, 35.34 24.51, 55.63 1.98 M2.23 69.51 C18.25 52.84, 35.05 31.42, 60.62 2.34 M2.23 69.51 C17.58 52.18, 33.64 33.42, 60.62 2.34 M2.62 75.16 C17.1 56.2, 31.96 40.07, 66.26 1.95 M2.62 75.16 C24.48 49.07, 46.3 23.85, 66.26 1.95 M2.36 81.55 C24.32 57.79, 41.68 33.55, 71.25 2.31 M2.36 81.55 C15.75 64.77, 30.49 48.43, 71.25 2.31 M2.76 87.2 C29.53 53.35, 58.71 21.02, 76.89 1.91 M2.76 87.2 C27.47 60.52, 50.01 33.66, 76.89 1.91 M2.49 93.59 C30.39 65.92, 54.94 33, 81.88 2.27 M2.49 93.59 C19.28 75.21, 36.25 56.86, 81.88 2.27 M2.23 99.99 C23.47 75.19, 45.61 48.82, 87.52 1.88 M2.23 99.99 C22.38 77.81, 39.72 56.44, 87.52 1.88 M2.63 105.64 C25.5 82.44, 48.33 53.24, 92.51 2.24 M2.63 105.64 C38.04 65.49, 73.72 25.11, 92.51 2.24 M2.37 112.03 C25.17 83.35, 50.79 57.74, 97.49 2.6 M2.37 112.03 C39.54 68.97, 76.47 26.61, 97.49 2.6 M2.76 117.68 C38.94 76.22, 76.83 30.72, 103.14 2.21 M2.76 117.68 C38.82 74.53, 76.12 32.17, 103.14 2.21 M2.5 124.07 C31.59 89.36, 57.94 58.92, 108.12 2.57 M2.5 124.07 C41.21 81.41, 78.58 36.8, 108.12 2.57 M2.24 130.47 C34.04 93.57, 62.41 56.01, 113.77 2.17 M2.24 130.47 C36.42 94.1, 68.39 55.28, 113.77 2.17 M2.63 136.11 C43.01 85.76, 88 40.56, 118.76 2.53 M2.63 136.11 C47.05 83.02, 94.87 29.48, 118.76 2.53 M2.37 142.51 C27.97 114.49, 50.4 83.34, 124.4 2.14 M2.37 142.51 C27.98 112.73, 53.54 82.18, 124.4 2.14 M2.11 148.91 C28.27 113.95, 58.41 81.99, 129.39 2.5 M2.11 148.91 C51.53 93.32, 99.37 35.95, 129.39 2.5 M2.5 154.55 C37.96 116.01, 69.1 77.68, 135.03 2.1 M2.5 154.55 C46.03 104.9, 87.64 57.17, 135.03 2.1 M2.24 160.95 C49.78 108.83, 92.64 54.5, 140.02 2.46 M2.24 160.95 C44.78 111.21, 87.51 61.62, 140.02 2.46 M2.64 166.59 C52.97 104.32, 106.95 46.64, 145 2.82 M2.64 166.59 C41.43 122.57, 80.3 79.07, 145 2.82 M2.38 172.99 C62.61 105.17, 120.48 38.67, 150.65 2.43 M2.38 172.99 C31.54 139.31, 61.63 104.74, 150.65 2.43 M2.11 179.39 C58.34 110.78, 116.42 45.38, 155.63 2.79 M2.11 179.39 C49.58 123.4, 97.32 68.22, 155.63 2.79 M2.51 185.03 C47.71 132.9, 93.59 79.99, 161.28 2.39 M2.51 185.03 C63.09 116.45, 121.61 47.65, 161.28 2.39 M2.25 191.43 C54.89 130.67, 106.18 69.33, 166.26 2.75 M2.25 191.43 C59.06 126.45, 116.47 61.17, 166.26 2.75 M1.99 197.83 C61.37 129.24, 123.56 60.44, 173.22 0.85 M1.99 197.83 C65.31 123.61, 128.63 48.94, 173.22 0.85 M2.38 203.47 C64.13 130.86, 124.45 59.09, 177.55 1.96 M2.38 203.47 C44.37 156.92, 85.37 109.62, 177.55 1.96 M2.12 209.87 C52.26 153.8, 101.33 99.65, 181.88 3.08 M2.12 209.87 C50.78 152.22, 100.97 94.69, 181.88 3.08 M2.51 215.51 C44.66 166.28, 86.22 117.21, 185.55 4.95 M2.51 215.51 C60.5 149.19, 117.81 81.87, 185.55 4.95 M2.25 221.91 C39.08 176.07, 78.86 134.24, 188.57 7.57 M2.25 221.91 C68.6 143.96, 135.36 67.59, 188.57 7.57 M1.99 228.31 C46.16 175.35, 89.44 124.44, 191.59 10.2 M1.99 228.31 C55.98 165.6, 112.56 101.78, 191.59 10.2 M2.39 233.95 C50.83 176.7, 102.68 118.92, 194.61 12.82 M2.39 233.95 C44.07 185.26, 86.21 135.6, 194.61 12.82 M2.12 240.35 C44.22 192, 88.35 143.4, 196.32 16.95 M2.12 240.35 C68.01 165.73, 133.04 90.01, 196.32 16.95 M0.55 248.26 C40.14 202.06, 81.26 157.82, 198.68 20.33 M0.55 248.26 C54.62 185.21, 108.56 122.43, 198.68 20.33 M0.95 253.9 C77.34 167.96, 153.81 79.95, 199.73 25.22 M0.95 253.9 C76.11 166.8, 151.8 79.46, 199.73 25.22 M2 258.79 C73.17 179.79, 142.85 99.3, 198.81 32.37 M2 258.79 C50.49 201.09, 101.28 142.66, 198.81 32.37 M3.7 262.92 C62.02 195.81, 121.31 127.1, 198.55 38.77 M3.7 262.92 C48.7 211.31, 94.56 158.13, 198.55 38.77 M4.75 267.81 C63.9 200.31, 124.53 132.56, 198.95 44.42 M4.75 267.81 C66.6 196.18, 128.37 125.43, 198.95 44.42 M7.77 270.43 C63.06 209.59, 117.34 145.88, 198.69 50.81 M7.77 270.43 C59.43 212.59, 109.81 155.61, 198.69 50.81 M10.79 273.06 C83.83 191.97, 156.42 106.57, 198.42 57.21 M10.79 273.06 C69.83 203.55, 130.55 133.49, 198.42 57.21 M13.15 276.44 C57.96 225.93, 101.7 174.36, 198.82 62.85 M13.15 276.44 C72.48 210.02, 130.35 144.13, 198.82 62.85 M16.83 278.31 C90.61 195.12, 161.23 112.14, 198.56 69.25 M16.83 278.31 C81.66 203.7, 145.86 127.65, 198.56 69.25 M20.5 280.18 C87.12 202.87, 152.2 125.23, 198.95 74.89 M20.5 280.18 C90.59 202.9, 158.72 124.09, 198.95 74.89 M25.49 280.54 C78.81 223.04, 126.45 165.7, 198.69 81.29 M25.49 280.54 C64.33 234.28, 105.04 188.2, 198.69 81.29 M29.82 281.65 C82.71 219.13, 137.75 158.15, 198.43 87.69 M29.82 281.65 C87.8 212.89, 146.94 145.23, 198.43 87.69 M34.81 282.01 C82.24 225.03, 129.4 171.42, 198.82 93.33 M34.81 282.01 C92.45 214.19, 150.02 148.94, 198.82 93.33 M39.8 282.37 C101.17 210.87, 164.22 139.35, 198.56 99.73 M39.8 282.37 C80.99 235.89, 120.78 189.35, 198.56 99.73 M45.44 281.98 C101.43 220.88, 155.78 156.27, 198.96 105.37 M45.44 281.98 C87.55 236.1, 127.44 190.26, 198.96 105.37 M50.43 282.34 C99.06 222.99, 148.94 166.8, 198.69 111.77 M50.43 282.34 C81.43 246.68, 110.67 212.1, 198.69 111.77 M56.07 281.94 C100.59 230.16, 146.24 178.38, 198.43 118.17 M56.07 281.94 C101.19 230.23, 145.01 180.42, 198.43 118.17 M61.06 282.3 C114.26 218.61, 169.79 155.67, 198.83 123.81 M61.06 282.3 C99.01 238.62, 135.05 194.71, 198.83 123.81 M66.7 281.91 C114.12 226.8, 164.14 172.95, 198.57 130.21 M66.7 281.91 C117.19 224.83, 167.08 166.29, 198.57 130.21 M71.69 282.27 C99.7 249.29, 131.55 217.94, 198.96 135.85 M71.69 282.27 C121.95 224.9, 173.56 165.33, 198.96 135.85 M76.67 282.63 C119.36 236, 163.28 185.67, 198.7 142.25 M76.67 282.63 C117.01 234.97, 159.05 187.81, 198.7 142.25 M82.32 282.23 C125.47 231.41, 168.67 179.9, 198.44 148.65 M82.32 282.23 C117.36 242.14, 151.89 201.62, 198.44 148.65 M87.3 282.59 C115.34 249.27, 142.89 215.75, 198.83 154.29 M87.3 282.59 C109.34 253.83, 133.62 227.54, 198.83 154.29 M92.95 282.2 C118.61 254.48, 144.65 223.52, 198.57 160.69 M92.95 282.2 C130.83 239.55, 166.83 197.48, 198.57 160.69 M97.93 282.56 C134.27 240.51, 171.7 197.9, 198.97 166.33 M97.93 282.56 C118.08 257.77, 138.91 235.01, 198.97 166.33 M103.58 282.16 C129.18 252.07, 158.4 222.55, 198.7 172.73 M103.58 282.16 C129.24 251.76, 155.24 221.31, 198.7 172.73 M108.56 282.52 C132.62 252.61, 158.05 222.53, 198.44 179.13 M108.56 282.52 C132.51 253.97, 158.55 225.87, 198.44 179.13 M114.21 282.13 C147.28 244.68, 175.91 209.14, 198.84 184.77 M114.21 282.13 C141.67 252.23, 166.3 220.69, 198.84 184.77 M119.19 282.49 C143.54 255.94, 165.21 230.87, 198.58 191.17 M119.19 282.49 C147.42 249.79, 177.55 215.44, 198.58 191.17 M124.84 282.1 C149.92 254.54, 173.1 226.45, 198.97 196.81 M124.84 282.1 C141.46 263.33, 157.97 245.67, 198.97 196.81 M129.82 282.46 C142.74 264.3, 157.18 251.87, 198.71 203.21 M129.82 282.46 C154.96 255.65, 179.5 225.52, 198.71 203.21 M135.47 282.06 C156.25 258.62, 175.52 235.74, 198.45 209.61 M135.47 282.06 C150.55 264.61, 167.27 245.19, 198.45 209.61 M140.45 282.42 C161.5 261.19, 180.47 236.06, 198.84 215.25 M140.45 282.42 C159.24 260.6, 179.54 238.2, 198.84 215.25 M146.1 282.03 C160.31 266.2, 173.33 248.34, 198.58 221.65 M146.1 282.03 C157.06 268.96, 170.08 253.81, 198.58 221.65 M151.08 282.39 C166.37 263.85, 182.9 248.22, 198.98 227.29 M151.08 282.39 C166.8 265.82, 180.98 247.19, 198.98 227.29 M156.73 281.99 C171.22 269.03, 180.74 251.24, 198.71 233.69 M156.73 281.99 C165.78 271.22, 175.2 260.93, 198.71 233.69 M161.71 282.35 C173.17 272.32, 182.23 258.46, 198.45 240.09 M161.71 282.35 C174.11 268.47, 184.63 256.52, 198.45 240.09 M168.01 281.2 C176.3 272.36, 181.24 264.01, 198.85 245.73 M168.01 281.2 C177.02 272.98, 184.04 262.29, 198.85 245.73 M173.66 280.81 C181.83 271.81, 188.42 262.71, 200.55 249.86 M173.66 280.81 C180.71 273.09, 187.4 263.03, 200.55 249.86 M180.61 278.9 C186.07 271.9, 190.46 265.3, 199.64 257.02 M180.61 278.9 C185.49 272.29, 191.33 265.86, 199.64 257.02" stroke="#40c057" stroke-width="0.5" fill="none"></path><path d="M32 0 M32 0 C62.44 -1.16, 89.7 -1.68, 166 0 M32 0 C81.72 0.91, 129.04 2.11, 166 0 M166 0 C185.8 -1.72, 198.37 9.01, 198 32 M166 0 C186.7 0.62, 196.86 11.79, 198 32 M198 32 C198.63 114.47, 197.99 199.32, 198 248 M198 32 C196.3 85.96, 197.69 140.17, 198 248 M198 248 C199.45 268.85, 186.48 281.46, 166 280 M198 248 C197.49 268.18, 188.87 278.14, 166 280 M166 280 C130.8 279.09, 97.15 277.98, 32 280 M166 280 C127.7 280.25, 89.83 280.19, 32 280 M32 280 C8.74 279.7, 1.89 269.47, 0 248 M32 280 C10.46 278.81, -2.22 268.56, 0 248 M0 248 C-1.74 170.77, -1.7 92, 0 32 M0 248 C-1.58 189.94, -1.36 133.09, 0 32 M0 32 C-0.4 11.4, 11.4 -0.82, 32 0 M0 32 C1.51 11.82, 12.12 -1.05, 32 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g stroke-linecap="round" transform="translate(564.8525020588318 398.10610387388687) rotate(0 78 23)"><path d="M11.14 1.41 L150.76 1.76 L154.27 3.15 L156.38 9.92 L155.74 37.68 L150.86 44.26 L145.42 45.99 L6.22 43.99 L3.87 41.21 L-1.76 36.52 L0.48 6.89 L1.6 4.68 L13.14 0.98" stroke="none" stroke-width="0" fill="#40c057"></path><path d="M11.5 0 M11.5 0 C55.01 1.15, 96.63 0.7, 144.5 0 M11.5 0 C51.63 1.74, 92.57 2.01, 144.5 0 M144.5 0 C153.66 -1.77, 156.55 4.17, 156 11.5 M144.5 0 C153.59 -0.67, 158.06 2.17, 156 11.5 M156 11.5 C156.66 16.83, 155.23 20.58, 156 34.5 M156 11.5 C155.26 20.45, 156.71 29.54, 156 34.5 M156 34.5 C156.13 40.8, 152.55 46.81, 144.5 46 M156 34.5 C155.73 39.99, 152.9 44.79, 144.5 46 M144.5 46 C108.81 44.74, 73.78 44.97, 11.5 46 M144.5 46 C103.35 47.03, 59.71 47.9, 11.5 46 M11.5 46 C2.01 44.24, -1.07 41.19, 0 34.5 M11.5 46 C2.05 43.81, -0.72 42.23, 0 34.5 M0 34.5 C0.99 25.93, 0.86 18.02, 0 11.5 M0 34.5 C-0.79 29.1, -0.88 24.27, 0 11.5 M0 11.5 C-0.44 5.77, 3.59 -0.05, 11.5 0 M0 11.5 C0.6 5.44, 2.66 -0.16, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(612.0025035847106 408.60610387388687) rotate(0 30.849998474121094 12.5)"><text x="30.849998474121094" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 1</text></g><g stroke-linecap="round" transform="translate(563.8525020588318 471.10610387388687) rotate(0 78 23)"><path d="M12.64 0.28 L150.09 1.83 L153.59 1.03 L155.17 8.68 L156.2 39.52 L151.26 43.09 L145.49 44.08 L4.53 44.61 L3.18 41.21 L-1.09 39 L1.82 9.79 L3.25 1.41 L12.45 1.1" stroke="none" stroke-width="0" fill="#40c057"></path><path d="M11.5 0 M11.5 0 C63.35 -1.03, 113.15 -1.84, 144.5 0 M11.5 0 C59.01 -1.93, 105.3 -0.88, 144.5 0 M144.5 0 C153.41 -0.58, 157.79 2.38, 156 11.5 M144.5 0 C149.89 -0.42, 157.13 4.64, 156 11.5 M156 11.5 C157.52 20.56, 153.98 25.14, 156 34.5 M156 11.5 C156.19 18.19, 156.32 26.66, 156 34.5 M156 34.5 C155.77 40.28, 152.8 44.95, 144.5 46 M156 34.5 C155.38 41.05, 150.5 46.73, 144.5 46 M144.5 46 C106.9 47.09, 70.36 47.72, 11.5 46 M144.5 46 C104.97 46.14, 66.74 46.53, 11.5 46 M11.5 46 C2.28 44.1, -0.63 42.22, 0 34.5 M11.5 46 C5.02 45.1, 1.32 43.2, 0 34.5 M0 34.5 C-1.95 28.82, -0.81 20.39, 0 11.5 M0 34.5 C-0.03 30.03, 0.06 23.6, 0 11.5 M0 11.5 C0.52 5.23, 2.82 -0.14, 11.5 0 M0 11.5 C1.75 2.78, 3.21 0.28, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(606.5925037372984 481.60610387388687) rotate(0 35.2599983215332 12.5)"><text x="35.2599983215332" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 2</text></g><g stroke-linecap="round" transform="translate(566.8525020588318 549.1061038738869) rotate(0 78 23)"><path d="M11.96 -1.85 L148.88 0.59 L154.05 2.86 L155.57 7.51 L156.27 37.62 L149.56 43.71 L144.8 44.09 L5.2 47.08 L4.52 44.11 L0.56 35.73 L1.13 9.9 L4.66 3.17 L12.84 0.11" stroke="none" stroke-width="0" fill="#40c057"></path><path d="M11.5 0 M11.5 0 C51.51 0.34, 91.04 2.12, 144.5 0 M11.5 0 C40.27 -0.51, 68.7 -0.95, 144.5 0 M144.5 0 C150.18 -0.37, 156.98 4.54, 156 11.5 M144.5 0 C152.98 -0.84, 155.81 5.68, 156 11.5 M156 11.5 C156.19 21.06, 156.88 28.52, 156 34.5 M156 11.5 C155.93 15.88, 156.36 21.63, 156 34.5 M156 34.5 C155.46 41.2, 150.71 46.64, 144.5 46 M156 34.5 C155.66 44.39, 152.09 46.37, 144.5 46 M144.5 46 C96.88 45.73, 51.18 45.35, 11.5 46 M144.5 46 C115.56 44.4, 87.85 45.38, 11.5 46 M11.5 46 C4.86 45.22, 1.15 43.07, 0 34.5 M11.5 46 C3.28 46.89, -0.35 40.03, 0 34.5 M0 34.5 C-1.19 25.22, -1.31 18.72, 0 11.5 M0 34.5 C0.29 26.07, -0.48 16.18, 0 11.5 M0 11.5 C1.52 2.91, 3.29 0.24, 11.5 0 M0 11.5 C-1.42 3.03, 3.51 -1.93, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(609.9025012958922 559.6061038738869) rotate(0 34.95000076293945 12.5)"><text x="34.95000076293945" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 3</text></g><g transform="translate(482.36663863335957 307.7688677100676) rotate(0 143.45001220703125 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Blue Deployment (old version)</text></g><g transform="translate(493.8630705300734 673.1438392940221) rotate(0 152.5699920654297 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Green Deployment (new version)</text></g><g stroke-linecap="round" transform="translate(168.09205930249547 272.71919600358564) rotate(269.9999999999999 130.8289993006931 40.14858179597991)"><path d="M20.62 -0.99 L242.56 1.67 L251.23 0.34 L256.43 4.59 L260.41 17.24 L260.68 58.98 L258.73 67.8 L253.11 79.46 L240.76 81.74 L19.59 79.45 L12.75 78.6 L1.82 73.79 L-1.3 63.96 L-0.33 14.13 L3.53 4.93 L9.86 0.06 L19.79 -1.58" stroke="none" stroke-width="0" fill="#ced4da"></path><path d="M20.07 0 M20.07 0 C97.64 -0.04, 171.98 0.45, 241.58 0 M20.07 0 C107.05 -0.67, 194.62 0.72, 241.58 0 M241.58 0 C255.3 -1.74, 260.03 8.3, 261.66 20.07 M241.58 0 C253.14 1.67, 260.87 7.97, 261.66 20.07 M261.66 20.07 C260.7 34.31, 261.02 49.55, 261.66 60.22 M261.66 20.07 C261.99 34.23, 261.04 46.9, 261.66 60.22 M261.66 60.22 C260.39 75.42, 255.89 78.39, 241.58 80.3 M261.66 60.22 C261.29 71.86, 256.53 78.98, 241.58 80.3 M241.58 80.3 C153.48 80.48, 65.79 80.02, 20.07 80.3 M241.58 80.3 C158.48 79.89, 74.7 79.31, 20.07 80.3 M20.07 80.3 C6.3 78.47, -1.88 73.58, 0 60.22 M20.07 80.3 C6.9 78.51, -1.8 73.81, 0 60.22 M0 60.22 C1.21 44.93, 0.86 28.53, 0 20.07 M0 60.22 C0.45 44.42, -0.43 30.76, 0 20.07 M0 20.07 C-0.44 4.81, 6.48 -1.4, 20.07 0 M0 20.07 C-0.13 5.89, 6.26 1.99, 20.07 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(227.33105463590343 300.36777779956554) rotate(269.9999999999999 71.59000396728516 12.5)"><text x="71.59000396728516" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Load Balancer</text></g><g transform="translate(23.299615479656893 338.1510010318354) rotate(0 28.5 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Users</text></g><g stroke-linecap="round" transform="translate(63.74243241887635 270.8911576974985) rotate(0 9.875171816384778 8.640775339336718)"><path d="M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.98 14.51 C7 9.89, 11.02 5.26, 14.13 1.68 M2.98 14.51 C6.2 10.8, 9.43 7.09, 14.13 1.68 M10.33 18.25 C12.75 15.46, 15.18 12.67, 19.51 7.69 M10.33 18.25 C12.65 15.58, 14.97 12.91, 19.51 7.69 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M15.81 15.34 C12.05 12.07, 8.29 8.8, 2.23 3.53 M15.81 15.34 C13.07 12.95, 10.32 10.56, 2.23 3.53 M20.31 8.65 C17.79 6.46, 15.27 4.27, 9.74 -0.54 M20.31 8.65 C16.35 5.21, 12.4 1.77, 9.74 -0.54" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M19.75 8.64 C19.75 9.14, 19.7 9.65, 19.6 10.14 C19.5 10.63, 19.35 11.13, 19.15 11.6 C18.96 12.07, 18.71 12.53, 18.43 12.96 C18.14 13.39, 17.81 13.81, 17.44 14.19 C17.07 14.58, 16.66 14.94, 16.22 15.26 C15.78 15.58, 15.31 15.87, 14.81 16.12 C14.32 16.37, 13.79 16.59, 13.25 16.76 C12.72 16.93, 12.15 17.06, 11.59 17.15 C11.03 17.24, 10.45 17.28, 9.88 17.28 C9.3 17.28, 8.72 17.24, 8.16 17.15 C7.6 17.06, 7.03 16.93, 6.5 16.76 C5.96 16.59, 5.43 16.37, 4.94 16.12 C4.44 15.87, 3.97 15.58, 3.53 15.26 C3.09 14.94, 2.68 14.58, 2.31 14.19 C1.94 13.81, 1.61 13.39, 1.32 12.96 C1.04 12.53, 0.79 12.07, 0.6 11.6 C0.4 11.13, 0.25 10.63, 0.15 10.14 C0.05 9.65, 0 9.14, 0 8.64 C0 8.14, 0.05 7.63, 0.15 7.14 C0.25 6.65, 0.4 6.16, 0.6 5.69 C0.79 5.22, 1.04 4.75, 1.32 4.32 C1.61 3.89, 1.94 3.47, 2.31 3.09 C2.68 2.7, 3.09 2.34, 3.53 2.02 C3.97 1.7, 4.44 1.41, 4.94 1.16 C5.43 0.91, 5.96 0.69, 6.5 0.52 C7.03 0.35, 7.6 0.22, 8.16 0.13 C8.72 0.04, 9.3 0, 9.88 0 C10.45 0, 11.03 0.04, 11.59 0.13 C12.15 0.22, 12.72 0.35, 13.25 0.52 C13.79 0.69, 14.32 0.91, 14.81 1.16 C15.31 1.41, 15.78 1.7, 16.22 2.02 C16.66 2.34, 17.07 2.7, 17.44 3.09 C17.81 3.47, 18.14 3.89, 18.43 4.32 C18.71 4.75, 18.96 5.22, 19.15 5.69 C19.35 6.16, 19.5 6.65, 19.6 7.14 C19.7 7.63, 19.73 8.39, 19.75 8.64 C19.78 8.89, 19.78 8.39, 19.75 8.64" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round" transform="translate(20.558758294554224 271.4742254811326) rotate(0 9.875171816384778 8.640775339336718)"><path d="M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.98 14.51 C7.15 9.71, 11.33 4.91, 14.13 1.68 M2.98 14.51 C6.26 10.74, 9.55 6.96, 14.13 1.68 M10.33 18.25 C13.34 14.78, 16.36 11.31, 19.51 7.69 M10.33 18.25 C13.27 14.87, 16.22 11.48, 19.51 7.69 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M15.81 15.34 C10.5 10.72, 5.18 6.1, 2.23 3.53 M15.81 15.34 C11.06 11.21, 6.31 7.08, 2.23 3.53 M20.31 8.65 C18 6.64, 15.7 4.64, 9.74 -0.54 M20.31 8.65 C17.52 6.23, 14.74 3.8, 9.74 -0.54" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M19.75 8.64 C19.75 9.14, 19.7 9.65, 19.6 10.14 C19.5 10.63, 19.35 11.13, 19.15 11.6 C18.96 12.07, 18.71 12.53, 18.43 12.96 C18.14 13.39, 17.81 13.81, 17.44 14.19 C17.07 14.58, 16.66 14.94, 16.22 15.26 C15.78 15.58, 15.31 15.87, 14.81 16.12 C14.32 16.37, 13.79 16.59, 13.25 16.76 C12.72 16.93, 12.15 17.06, 11.59 17.15 C11.03 17.24, 10.45 17.28, 9.88 17.28 C9.3 17.28, 8.72 17.24, 8.16 17.15 C7.6 17.06, 7.03 16.93, 6.5 16.76 C5.96 16.59, 5.43 16.37, 4.94 16.12 C4.44 15.87, 3.97 15.58, 3.53 15.26 C3.09 14.94, 2.68 14.58, 2.31 14.19 C1.94 13.81, 1.61 13.39, 1.32 12.96 C1.04 12.53, 0.79 12.07, 0.6 11.6 C0.4 11.13, 0.25 10.63, 0.15 10.14 C0.05 9.65, 0 9.14, 0 8.64 C0 8.14, 0.05 7.63, 0.15 7.14 C0.25 6.65, 0.4 6.16, 0.6 5.69 C0.79 5.22, 1.04 4.75, 1.32 4.32 C1.61 3.89, 1.94 3.47, 2.31 3.09 C2.68 2.7, 3.09 2.34, 3.53 2.02 C3.97 1.7, 4.44 1.41, 4.94 1.16 C5.43 0.91, 5.96 0.69, 6.5 0.52 C7.03 0.35, 7.6 0.22, 8.16 0.13 C8.72 0.04, 9.3 0, 9.88 0 C10.45 0, 11.03 0.04, 11.59 0.13 C12.15 0.22, 12.72 0.35, 13.25 0.52 C13.79 0.69, 14.32 0.91, 14.81 1.16 C15.31 1.41, 15.78 1.7, 16.22 2.02 C16.66 2.34, 17.07 2.7, 17.44 3.09 C17.81 3.47, 18.14 3.89, 18.43 4.32 C18.71 4.75, 18.96 5.22, 19.15 5.69 C19.35 6.16, 19.5 6.65, 19.6 7.14 C19.7 7.63, 19.73 8.39, 19.75 8.64 C19.78 8.89, 19.78 8.39, 19.75 8.64" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round"><g transform="translate(31.01057830181864 330.4052612187822) rotate(0 21.90843989373377 -18.494048425191174)" fill-rule="evenodd"><path d="M11.93 -33.36 C11.93 -33.36, 11.93 -33.36, 11.93 -33.36 M11.93 -33.36 C11.93 -33.36, 11.93 -33.36, 11.93 -33.36 M6.81 -15.28 C13.91 -23.45, 21.01 -31.62, 25.18 -36.41 M6.81 -15.28 C12.41 -21.72, 18 -28.16, 25.18 -36.41 M2.35 2.04 C13.9 -11.24, 25.44 -24.52, 31.87 -31.92 M2.35 2.04 C10.27 -7.07, 18.19 -16.17, 31.87 -31.92 M12.98 2.01 C20.25 -6.35, 27.52 -14.71, 37.25 -25.92 M12.98 2.01 C18.57 -4.42, 24.16 -10.85, 37.25 -25.92 M23.61 1.97 C27.65 -2.68, 31.7 -7.33, 41.32 -18.4 M23.61 1.97 C29.7 -5.03, 35.8 -12.04, 41.32 -18.4 M34.9 1.19 C37.26 -1.53, 39.62 -4.24, 46.05 -11.64 M34.9 1.19 C37.89 -2.26, 40.88 -5.7, 46.05 -11.64 M0 0 C0 0, 0 0, 0 0 M0 0 C0 0, 0 0, 0 0 M12.04 -0.13 C9.55 -2.3, 7.06 -4.46, 1.47 -9.32 M12.04 -0.13 C9.46 -2.38, 6.88 -4.62, 1.47 -9.32 M24.08 -0.27 C16.97 -6.45, 9.86 -12.63, 2.95 -18.64 M24.08 -0.27 C17.96 -5.59, 11.84 -10.91, 2.95 -18.64 M34.61 -1.71 C26.93 -8.39, 19.25 -15.07, 5.93 -26.64 M34.61 -1.71 C23.82 -11.1, 13.02 -20.48, 5.93 -26.64 M43.64 -4.47 C36.36 -10.79, 29.08 -17.12, 11.18 -32.68 M43.64 -4.47 C31.61 -14.92, 19.59 -25.37, 11.18 -32.68 M42.85 -15.76 C35.5 -22.14, 28.15 -28.53, 17.19 -38.06 M42.85 -15.76 C33.23 -24.11, 23.61 -32.47, 17.19 -38.06" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C0.78 -4.11, 1.34 -18.46, 4.68 -24.67 C8.03 -30.87, 14.94 -36.78, 20.07 -37.23 C25.2 -37.68, 31.83 -33.14, 35.45 -27.36 C39.07 -21.58, 47.71 -7.12, 41.81 -2.56 C35.9 2, 6.97 -0.43, 0 0 M0 0 C0.78 -4.11, 1.34 -18.46, 4.68 -24.67 C8.03 -30.87, 14.94 -36.78, 20.07 -37.23 C25.2 -37.68, 31.83 -33.14, 35.45 -27.36 C39.07 -21.58, 47.71 -7.12, 41.81 -2.56 C35.9 2, 6.97 -0.43, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round" transform="translate(41.49670045262869 273.83074989894516) rotate(0 10.702336545928873 9.364544477687804)"><path d="M2.43 3.43 C2.43 3.43, 2.43 3.43, 2.43 3.43 M2.43 3.43 C2.43 3.43, 2.43 3.43, 2.43 3.43 M2.56 15.48 C5.33 12.28, 8.11 9.09, 15.02 1.14 M2.56 15.48 C5.85 11.69, 9.15 7.9, 15.02 1.14 M9.91 19.21 C12.33 16.43, 14.76 13.64, 21.06 6.38 M9.91 19.21 C12.3 16.46, 14.7 13.7, 21.06 6.38 M4.02 16.71 C4.02 16.71, 4.02 16.71, 4.02 16.71 M4.02 16.71 C4.02 16.71, 4.02 16.71, 4.02 16.71 M16.82 17.23 C11.07 12.24, 5.33 7.25, 1.72 4.11 M16.82 17.23 C11.08 12.25, 5.34 7.26, 1.72 4.11 M21.31 10.54 C17.49 7.22, 13.67 3.9, 9.24 0.04 M21.31 10.54 C17.24 7, 13.16 3.46, 9.24 0.04" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M21.4 9.36 C21.4 9.91, 21.35 10.46, 21.24 10.99 C21.13 11.52, 20.97 12.06, 20.76 12.57 C20.55 13.08, 20.28 13.58, 19.97 14.05 C19.66 14.52, 19.3 14.97, 18.9 15.38 C18.5 15.8, 18.06 16.19, 17.58 16.54 C17.11 16.89, 16.59 17.2, 16.05 17.47 C15.52 17.75, 14.94 17.98, 14.36 18.16 C13.78 18.35, 13.17 18.49, 12.56 18.59 C11.95 18.68, 11.32 18.73, 10.7 18.73 C10.08 18.73, 9.45 18.68, 8.84 18.59 C8.23 18.49, 7.62 18.35, 7.04 18.16 C6.46 17.98, 5.89 17.75, 5.35 17.47 C4.81 17.2, 4.3 16.89, 3.82 16.54 C3.35 16.19, 2.9 15.8, 2.5 15.38 C2.11 14.97, 1.74 14.52, 1.43 14.05 C1.12 13.58, 0.86 13.08, 0.65 12.57 C0.43 12.06, 0.27 11.52, 0.16 10.99 C0.06 10.46, 0 9.91, 0 9.36 C0 8.82, 0.06 8.27, 0.16 7.74 C0.27 7.2, 0.43 6.67, 0.65 6.16 C0.86 5.65, 1.12 5.15, 1.43 4.68 C1.74 4.21, 2.11 3.76, 2.5 3.35 C2.9 2.93, 3.35 2.54, 3.82 2.19 C4.3 1.84, 4.81 1.53, 5.35 1.25 C5.89 0.98, 6.46 0.75, 7.04 0.56 C7.62 0.38, 8.23 0.24, 8.84 0.14 C9.45 0.05, 10.08 0, 10.7 0 C11.32 0, 11.95 0.05, 12.56 0.14 C13.17 0.24, 13.78 0.38, 14.36 0.56 C14.94 0.75, 15.52 0.98, 16.05 1.25 C16.59 1.53, 17.11 1.84, 17.58 2.19 C18.06 2.54, 18.5 2.93, 18.9 3.35 C19.3 3.76, 19.66 4.21, 19.97 4.68 C20.28 5.15, 20.55 5.65, 20.76 6.16 C20.97 6.67, 21.13 7.2, 21.24 7.74 C21.35 8.27, 21.38 9.09, 21.4 9.36 C21.43 9.64, 21.43 9.09, 21.4 9.36" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round"><g transform="translate(60.161913756269655 296.73619653372924) rotate(0 16.71865860152218 9.921154001040179)" fill-rule="evenodd"><path d="M0 0 C0 0, 0 0, 0 0 M0 0 C0 0, 0 0, 0 0 M6.04 5.25 C8.63 2.26, 11.23 -0.72, 17.85 -8.34 M6.04 5.25 C9.44 1.34, 12.84 -2.57, 17.85 -8.34 M12.08 10.5 C16.92 4.93, 21.76 -0.64, 25.2 -4.6 M12.08 10.5 C14.86 7.29, 17.65 4.09, 25.2 -4.6 M15.49 18.76 C21.36 12.01, 27.24 5.25, 31.23 0.65 M15.49 18.76 C20.86 12.58, 26.24 6.4, 31.23 0.65 M16.93 29.3 C23.03 22.28, 29.13 15.26, 33.34 10.43 M16.93 29.3 C22.34 23.08, 27.75 16.86, 33.34 10.43 M29.53 27 C31.49 24.74, 33.45 22.49, 34.78 20.96 M29.53 27 C31.57 24.66, 33.6 22.31, 34.78 20.96 M14.43 27.6 C14.43 27.6, 14.43 27.6, 14.43 27.6 M14.43 27.6 C14.43 27.6, 14.43 27.6, 14.43 27.6 M25.72 26.82 C22.82 24.29, 19.92 21.77, 16.66 18.94 M25.72 26.82 C23.31 24.72, 20.91 22.63, 16.66 18.94 M33.98 23.4 C27.09 17.41, 20.2 11.42, 3.04 -3.5 M33.98 23.4 C26.81 17.17, 19.64 10.93, 3.04 -3.5 M36.97 15.4 C28.88 8.37, 20.8 1.34, 9.8 -8.22 M36.97 15.4 C31.4 10.56, 25.83 5.72, 9.8 -8.22" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C0.86 -0.93, 3.58 -4.18, 5.17 -5.57 C6.77 -6.97, 7.56 -7.83, 9.55 -8.36 C11.54 -8.89, 14.99 -8.89, 17.12 -8.76 C19.24 -8.62, 20.83 -8.43, 22.29 -7.56 C23.75 -6.7, 24.88 -5.11, 25.87 -3.58 C26.87 -2.06, 27.47 -0.33, 28.26 1.59 C29.06 3.52, 29.92 5.84, 30.65 7.96 C31.38 10.08, 32.18 12.41, 32.64 14.33 C33.11 16.25, 33.44 17.78, 33.44 19.51 C33.44 21.23, 33.3 23.42, 32.64 24.68 C31.98 25.94, 30.72 26.47, 29.46 27.07 C28.2 27.67, 26.87 28, 25.08 28.26 C23.29 28.53, 20.43 28.73, 18.71 28.66 C16.98 28.59, 15.46 28.93, 14.73 27.86 C14 26.8, 14.66 23.82, 14.33 22.29 C14 20.77, 13.47 20.23, 12.74 18.71 C12.01 17.18, 11.08 15.33, 9.95 13.14 C8.82 10.95, 7.63 7.76, 5.97 5.57 C4.31 3.38, 1 0.93, 0 0 M0 0 C0.86 -0.93, 3.58 -4.18, 5.17 -5.57 C6.77 -6.97, 7.56 -7.83, 9.55 -8.36 C11.54 -8.89, 14.99 -8.89, 17.12 -8.76 C19.24 -8.62, 20.83 -8.43, 22.29 -7.56 C23.75 -6.7, 24.88 -5.11, 25.87 -3.58 C26.87 -2.06, 27.47 -0.33, 28.26 1.59 C29.06 3.52, 29.92 5.84, 30.65 7.96 C31.38 10.08, 32.18 12.41, 32.64 14.33 C33.11 16.25, 33.44 17.78, 33.44 19.51 C33.44 21.23, 33.3 23.42, 32.64 24.68 C31.98 25.94, 30.72 26.47, 29.46 27.07 C28.2 27.67, 26.87 28, 25.08 28.26 C23.29 28.53, 20.43 28.73, 18.71 28.66 C16.98 28.59, 15.46 28.93, 14.73 27.86 C14 26.8, 14.66 23.82, 14.33 22.29 C14 20.77, 13.47 20.23, 12.74 18.71 C12.01 17.18, 11.08 15.33, 9.95 13.14 C8.82 10.95, 7.63 7.76, 5.97 5.57 C4.31 3.38, 1 0.93, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(42.243127302935676 296.7243206303248) rotate(0 -16.121563651467838 12.19394740044196)" fill-rule="evenodd"><path d="M-24.42 -2.68 C-24.42 -2.68, -24.42 -2.68, -24.42 -2.68 M-24.42 -2.68 C-24.42 -2.68, -24.42 -2.68, -24.42 -2.68 M-26.26 11.62 C-20.98 5.55, -15.7 -0.52, -12.48 -4.23 M-26.26 11.62 C-22.34 7.12, -18.43 2.61, -12.48 -4.23 M-29.41 27.44 C-19.17 15.66, -8.93 3.88, -2.51 -3.51 M-29.41 27.44 C-19.18 15.67, -8.95 3.91, -2.51 -3.51 M-22.71 31.93 C-18.15 26.68, -13.58 21.42, -8.28 15.33 M-22.71 31.93 C-17.84 26.33, -12.97 20.73, -8.28 15.33 M-12.74 32.65 C-12.11 31.92, -11.48 31.2, -10.77 30.39 M-12.74 32.65 C-12.17 31.99, -11.6 31.34, -10.77 30.39 M-31.63 25.72 C-31.63 25.72, -31.63 25.72, -31.63 25.72 M-31.63 25.72 C-31.63 25.72, -31.63 25.72, -31.63 25.72 M-13.55 30.83 C-19.05 26.05, -24.55 21.27, -29.4 17.05 M-13.55 30.83 C-19.12 25.99, -24.69 21.15, -29.4 17.05 M-6.79 26.11 C-14.23 19.64, -21.67 13.18, -27.92 7.74 M-6.79 26.11 C-14.66 19.26, -22.53 12.42, -27.92 7.74 M-8.34 14.16 C-12.48 10.56, -16.62 6.97, -24.94 -0.27 M-8.34 14.16 C-12.66 10.41, -16.98 6.65, -24.94 -0.27 M-4.6 6.81 C-8.74 3.22, -12.87 -0.38, -20.45 -6.96 M-4.6 6.81 C-9.74 2.34, -14.89 -2.13, -20.45 -6.96 M-0.1 0.12 C-2.69 -2.13, -5.29 -4.38, -12.93 -11.03 M-0.1 0.12 C-4.04 -3.3, -7.98 -6.72, -12.93 -11.03" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C-0.66 -0.73, -2.59 -3.18, -3.98 -4.38 C-5.37 -5.57, -6.37 -6.63, -8.36 -7.17 C-10.35 -7.7, -13.8 -7.7, -15.92 -7.56 C-18.05 -7.43, -19.64 -7.23, -21.1 -6.37 C-22.56 -5.51, -23.68 -3.91, -24.68 -2.39 C-25.68 -0.86, -26.27 0.86, -27.07 2.79 C-27.86 4.71, -28.73 7.03, -29.46 9.16 C-30.19 11.28, -30.98 13.6, -31.45 15.52 C-31.91 17.45, -32.24 18.97, -32.24 20.7 C-32.24 22.42, -32.11 24.61, -31.45 25.87 C-30.78 27.13, -29.46 27.53, -28.26 28.26 C-27.07 28.99, -26.01 29.72, -24.28 30.25 C-22.56 30.78, -20.1 31.25, -17.91 31.45 C-15.72 31.65, -12.41 32.64, -11.15 31.45 C-9.89 30.25, -10.62 26.07, -10.35 24.28 C-10.08 22.49, -9.89 22.29, -9.55 20.7 C-9.22 19.11, -9.16 17.05, -8.36 14.73 C-7.56 12.41, -6.17 9.22, -4.78 6.77 C-3.38 4.31, -0.8 1.13, 0 0 M0 0 C-0.66 -0.73, -2.59 -3.18, -3.98 -4.38 C-5.37 -5.57, -6.37 -6.63, -8.36 -7.17 C-10.35 -7.7, -13.8 -7.7, -15.92 -7.56 C-18.05 -7.43, -19.64 -7.23, -21.1 -6.37 C-22.56 -5.51, -23.68 -3.91, -24.68 -2.39 C-25.68 -0.86, -26.27 0.86, -27.07 2.79 C-27.86 4.71, -28.73 7.03, -29.46 9.16 C-30.19 11.28, -30.98 13.6, -31.45 15.52 C-31.91 17.45, -32.24 18.97, -32.24 20.7 C-32.24 22.42, -32.11 24.61, -31.45 25.87 C-30.78 27.13, -29.46 27.53, -28.26 28.26 C-27.07 28.99, -26.01 29.72, -24.28 30.25 C-22.56 30.78, -20.1 31.25, -17.91 31.45 C-15.72 31.65, -12.41 32.64, -11.15 31.45 C-9.89 30.25, -10.62 26.07, -10.35 24.28 C-10.08 22.49, -9.89 22.29, -9.55 20.7 C-9.22 19.11, -9.16 17.05, -8.36 14.73 C-7.56 12.41, -6.17 9.22, -4.78 6.77 C-3.38 4.31, -0.8 1.13, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(109.94583739107617 301.79230695929556) rotate(0 69.50582442546883 -0.21775699114179936)"><path d="M0.46 -1.13 C23.33 -1.4, 114.38 -1.34, 137.53 -1.27 M-0.75 0.89 C22.46 0.81, 116.46 0.92, 139.77 0.32" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(109.94583739107617 301.79230695929556) rotate(0 69.50582442546883 -0.21775699114179936)"><path d="M109.8 9.35 C121 8.85, 131.08 2.86, 137.83 -1.25 M111.78 10.88 C117.49 7.38, 126.2 6.02, 140.47 0.9" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(109.94583739107617 301.79230695929556) rotate(0 69.50582442546883 -0.21775699114179936)"><path d="M109.59 -11.17 C120.92 -4.98, 131.06 -4.27, 137.83 -1.25 M111.57 -9.64 C117.47 -8.16, 126.22 -4.54, 140.47 0.9" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(346.6840266018544 299.023439249228) rotate(0 91.89297819086164 -68.33590292315091)"><path d="M0.9 -0.81 C31.56 -23.98, 153.71 -115.18, 183.87 -138.05 M-0.08 1.37 C30.53 -21.76, 152.78 -113.94, 183.51 -137.03" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(346.6840266018544 299.023439249228) rotate(0 91.89297819086164 -68.33590292315091)"><path d="M165.81 -110 C170.08 -120.78, 174.95 -127.54, 181.61 -136.13 M168.12 -110.89 C173.61 -120.46, 178.74 -128.9, 184.02 -137.04" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(346.6840266018544 299.023439249228) rotate(0 91.89297819086164 -68.33590292315091)"><path d="M153.47 -126.39 C161.47 -132.49, 169.93 -134.47, 181.61 -136.13 M155.78 -127.28 C165.69 -131.12, 175.21 -133.74, 184.02 -137.04" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(345.2995927468206 337.7875871901741) rotate(0 97.23161390106503 70.46981831922541)"><path d="M0.56 -1.07 C32.89 22.77, 161.75 117.94, 193.9 142.01" stroke="#000000" stroke-width="1.5" fill="none" stroke-dasharray="8 9"></path></g><g transform="translate(345.2995927468206 337.7875871901741) rotate(0 97.23161390106503 70.46981831922541)"><path d="M163.37 133.57 C172.52 135.21, 183.21 137.65, 194.25 140.82" stroke="#000000" stroke-width="1.5" fill="none"></path></g><g transform="translate(345.2995927468206 337.7875871901741) rotate(0 97.23161390106503 70.46981831922541)"><path d="M175.61 117.09 C181.04 123.62, 188.14 130.88, 194.25 140.82" stroke="#000000" stroke-width="1.5" fill="none"></path></g></g><mask></mask><g transform="translate(344.2668979542183 413.3442172592771) rotate(36.6751652732473 77.04073370879092 7.65143055727205)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="12.24228889163527px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">switch traffic when ready</text></g></svg>
\ No newline at end of file
diff --git a/site/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg b/site/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg
new file mode 100644
index 0000000000..f0517c366a
--- /dev/null
+++ b/site/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg
@@ -0,0 +1,16 @@
+<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1035.2128615642703 288.10009003177834" width="2070.4257231285405" height="576.2001800635567">
+  <!-- svg-source:excalidraw -->
+  
+  <defs>
+    <style class="style-fonts">
+      @font-face {
+        font-family: "Virgil";
+        src: url("https://excalidraw.com/Virgil.woff2");
+      }
+      @font-face {
+        font-family: "Cascadia";
+        src: url("https://excalidraw.com/Cascadia.woff2");
+      }
+    </style>
+  </defs>
+  <rect x="0" y="0" width="1035.2128615642703" height="288.10009003177834" fill="#ffffff"></rect><g stroke-linecap="round" transform="translate(572.5859715004883 10) rotate(0 78 23)"><path d="M12.29 1.87 L150.88 2.14 L153.22 1.18 L154.64 8.07 L153.7 39.91 L152.04 44.73 L143.77 45.85 L5.31 44.12 L4.18 42.97 L0.4 38.48 L0.52 9.61 L2.2 3.43 L10.86 -1.47" stroke="none" stroke-width="0" fill="#40c057"></path><path d="M11.5 0 M11.5 0 C55.86 -0.94, 104.69 2.02, 144.5 0 M11.5 0 C52.5 -1.59, 93.8 -0.09, 144.5 0 M144.5 0 C153.34 -1.84, 156.21 3.91, 156 11.5 M144.5 0 C151.21 2.01, 158.25 6.11, 156 11.5 M156 11.5 C156.38 20.39, 157.4 27.42, 156 34.5 M156 11.5 C156.47 16.53, 156.46 23.82, 156 34.5 M156 34.5 C154.88 41.69, 151.57 46.75, 144.5 46 M156 34.5 C153.99 39.99, 151.21 46.01, 144.5 46 M144.5 46 C107.85 47.16, 73.45 44.78, 11.5 46 M144.5 46 C96.28 45.69, 48.24 45.73, 11.5 46 M11.5 46 C2.44 46.17, -0.11 43.81, 0 34.5 M11.5 46 C5.29 45.32, -1.71 40.21, 0 34.5 M0 34.5 C0.18 27.03, 0.55 23.73, 0 11.5 M0 34.5 C0.9 26.51, 0.2 17.09, 0 11.5 M0 11.5 C0.6 2.61, 3.13 -0.22, 11.5 0 M0 11.5 C-0.84 6.1, 2.16 -0.68, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(619.7359730263672 20.5) rotate(0 30.849998474121094 12.5)"><text x="30.849998474121094" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 1</text></g><g stroke-linecap="round" transform="translate(575.3548392105558 84.38443385503382) rotate(0 78 23)"><path d="M11.59 -1.69 L148.35 -0.01 L151.54 3.25 L156.36 9.15 L154.55 39.39 L150.35 43.23 L145.8 45.84 L6.69 46.57 L3.22 43.93 L-0.5 37.75 L-0.46 7.34 L3.82 4.75 L9.99 -1.83" stroke="none" stroke-width="0" fill="#228be6"></path><path d="M11.5 0 M11.5 0 C38.68 1.09, 66.68 -1.3, 144.5 0 M11.5 0 C41.89 -1.91, 71.22 -0.95, 144.5 0 M144.5 0 C151.34 1.75, 157.95 5.81, 156 11.5 M144.5 0 C153.62 -1, 156.37 4.38, 156 11.5 M156 11.5 C155.37 20.22, 155.58 27.19, 156 34.5 M156 11.5 C155.52 15.99, 155.78 21.32, 156 34.5 M156 34.5 C154.25 40.28, 151.33 46.01, 144.5 46 M156 34.5 C155.17 40.86, 153.07 44.2, 144.5 46 M144.5 46 C101.63 46.03, 54.75 45.61, 11.5 46 M144.5 46 C95.7 46.96, 48.24 47.69, 11.5 46 M11.5 46 C5.1 45.41, -1.49 40.47, 0 34.5 M11.5 46 C3.1 47.84, 1.38 42.59, 0 34.5 M0 34.5 C1.16 27.3, 0.05 25.09, 0 11.5 M0 34.5 C0.3 26.21, -0.35 19.03, 0 11.5 M0 11.5 C-0.73 5.8, 2.38 -0.6, 11.5 0 M0 11.5 C-0.4 5.04, 5.33 -2.23, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(618.0948408890226 94.88443385503382) rotate(0 35.2599983215332 12.5)"><text x="35.2599983215332" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 2</text></g><g stroke-linecap="round" transform="translate(577.3548392105558 151.3089630147635) rotate(0 78 23)"><path d="M9.92 0.38 L150.07 1.07 L152.39 2.73 L154.66 7.65 L156.58 39.38 L151.73 45.67 L144.84 46.8 L5.79 45.84 L2.24 41.66 L1.13 39.07 L-1.33 6.98 L0.93 3.68 L12.52 0.21" stroke="none" stroke-width="0" fill="#228be6"></path><path d="M11.5 0 M11.5 0 C61.59 -0.25, 116.2 1.59, 144.5 0 M11.5 0 C38.72 0.83, 67.74 0.94, 144.5 0 M144.5 0 C153.43 -0.87, 156.32 4.31, 156 11.5 M144.5 0 C152.78 1.72, 155.09 2.91, 156 11.5 M156 11.5 C154.04 20.43, 156.68 26.95, 156 34.5 M156 11.5 C155.06 16.91, 155.51 24.21, 156 34.5 M156 34.5 C155.28 41.03, 152.95 44.44, 144.5 46 M156 34.5 C156.74 41.17, 150.17 47.5, 144.5 46 M144.5 46 C97.97 48.39, 50.29 45.11, 11.5 46 M144.5 46 C104.12 46.79, 61.74 46.24, 11.5 46 M11.5 46 C3.2 47.6, 1.2 42.53, 0 34.5 M11.5 46 C2.34 46.84, 1.8 43.59, 0 34.5 M0 34.5 C0.66 29.65, -1.54 25.43, 0 11.5 M0 34.5 C-0.28 30, -0.65 23.22, 0 11.5 M0 11.5 C-0.35 4.88, 5.14 -1.94, 11.5 0 M0 11.5 C0.14 5.14, 1.87 -0.24, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(620.4048384476164 161.8089630147635) rotate(0 34.95000076293945 12.5)"><text x="34.95000076293945" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 3</text></g><g stroke-linecap="round" transform="translate(169.47649315752938 107.12250893510526) rotate(269.9999999999999 130.8289993006931 40.14858179597991)"><path d="M18.57 -1.83 L239.64 0.8 L251.38 1.47 L258.4 6.27 L260.72 13.85 L260.99 61.7 L261.58 67.16 L254.02 77.55 L240.75 82.05 L22.03 82.28 L12.56 78.17 L3.15 72.93 L0.85 66.43 L-0.48 14.57 L6.22 4.42 L11.95 -0.64 L20.72 0.74" stroke="none" stroke-width="0" fill="#ced4da"></path><path d="M20.07 0 M20.07 0 C74.8 -0.94, 126.59 -0.15, 241.58 0 M20.07 0 C86.95 0.41, 153.42 0.71, 241.58 0 M241.58 0 C253.23 1.31, 262.84 5.29, 261.66 20.07 M241.58 0 C255.85 1.42, 263.82 8.2, 261.66 20.07 M261.66 20.07 C263.33 30.59, 261.1 37.08, 261.66 60.22 M261.66 20.07 C262.13 28.89, 260.88 37.71, 261.66 60.22 M261.66 60.22 C263.23 74.85, 253.17 80.43, 241.58 80.3 M261.66 60.22 C263.26 74.38, 254.95 78.54, 241.58 80.3 M241.58 80.3 C168.3 78.99, 97.1 78.37, 20.07 80.3 M241.58 80.3 C182.29 80.46, 121.92 81.79, 20.07 80.3 M20.07 80.3 C4.99 80.09, 1.26 73.31, 0 60.22 M20.07 80.3 C8.3 82.59, -0.29 74.26, 0 60.22 M0 60.22 C-0.39 44.11, -0.18 29.93, 0 20.07 M0 60.22 C-0.9 47.97, 0.2 34.67, 0 20.07 M0 20.07 C-1.03 8.01, 8.05 -1.11, 20.07 0 M0 20.07 C0.42 7.75, 5.98 0.49, 20.07 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(228.71548849093733 134.77109073108517) rotate(269.9999999999999 71.59000396728516 12.5)"><text x="71.59000396728516" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Load Balancer</text></g><g transform="translate(23.299615479656723 172.554313963355) rotate(0 28.5 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Users</text></g><g stroke-linecap="round" transform="translate(63.742432418876206 105.29447062901812) rotate(0 9.87517181638475 8.64077533933672)"><path d="M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.98 14.51 C6.68 10.25, 10.39 5.99, 14.13 1.68 M2.98 14.51 C5.69 11.39, 8.4 8.27, 14.13 1.68 M10.33 18.25 C13.95 14.09, 17.57 9.92, 19.51 7.69 M10.33 18.25 C13.82 14.24, 17.31 10.22, 19.51 7.69 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M15.81 15.34 C11.91 11.95, 8.01 8.55, 2.23 3.53 M15.81 15.34 C12.07 12.08, 8.32 8.83, 2.23 3.53 M20.31 8.65 C17.47 6.18, 14.62 3.71, 9.74 -0.54 M20.31 8.65 C16.41 5.25, 12.5 1.86, 9.74 -0.54" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M19.75 8.64 C19.75 9.14, 19.7 9.65, 19.6 10.14 C19.5 10.63, 19.35 11.13, 19.15 11.6 C18.96 12.07, 18.71 12.53, 18.43 12.96 C18.14 13.39, 17.81 13.81, 17.44 14.19 C17.07 14.58, 16.66 14.94, 16.22 15.26 C15.78 15.58, 15.31 15.87, 14.81 16.12 C14.32 16.37, 13.79 16.59, 13.25 16.76 C12.72 16.93, 12.15 17.06, 11.59 17.15 C11.03 17.24, 10.45 17.28, 9.88 17.28 C9.3 17.28, 8.72 17.24, 8.16 17.15 C7.6 17.06, 7.03 16.93, 6.5 16.76 C5.96 16.59, 5.43 16.37, 4.94 16.12 C4.44 15.87, 3.97 15.58, 3.53 15.26 C3.09 14.94, 2.68 14.58, 2.31 14.19 C1.94 13.81, 1.61 13.39, 1.32 12.96 C1.04 12.53, 0.79 12.07, 0.6 11.6 C0.4 11.13, 0.25 10.63, 0.15 10.14 C0.05 9.65, 0 9.14, 0 8.64 C0 8.14, 0.05 7.63, 0.15 7.14 C0.25 6.65, 0.4 6.16, 0.6 5.69 C0.79 5.22, 1.04 4.75, 1.32 4.32 C1.61 3.89, 1.94 3.47, 2.31 3.09 C2.68 2.7, 3.09 2.34, 3.53 2.02 C3.97 1.7, 4.44 1.41, 4.94 1.16 C5.43 0.91, 5.96 0.69, 6.5 0.52 C7.03 0.35, 7.6 0.22, 8.16 0.13 C8.72 0.04, 9.3 0, 9.88 0 C10.45 0, 11.03 0.04, 11.59 0.13 C12.15 0.22, 12.72 0.35, 13.25 0.52 C13.79 0.69, 14.32 0.91, 14.81 1.16 C15.31 1.41, 15.78 1.7, 16.22 2.02 C16.66 2.34, 17.07 2.7, 17.44 3.09 C17.81 3.47, 18.14 3.89, 18.43 4.32 C18.71 4.75, 18.96 5.22, 19.15 5.69 C19.35 6.16, 19.5 6.65, 19.6 7.14 C19.7 7.63, 19.73 8.39, 19.75 8.64 C19.78 8.89, 19.78 8.39, 19.75 8.64" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round" transform="translate(20.55875829455408 105.8775384126522) rotate(0 9.87517181638475 8.64077533933672)"><path d="M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.98 14.51 C5.7 11.38, 8.42 8.25, 14.13 1.68 M2.98 14.51 C5.45 11.67, 7.93 8.82, 14.13 1.68 M10.33 18.25 C12.44 15.82, 14.56 13.39, 19.51 7.69 M10.33 18.25 C13.25 14.89, 16.17 11.53, 19.51 7.69 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M15.81 15.34 C10.62 10.82, 5.42 6.3, 2.23 3.53 M15.81 15.34 C11.57 11.65, 7.33 7.96, 2.23 3.53 M20.31 8.65 C17.85 6.51, 15.39 4.37, 9.74 -0.54 M20.31 8.65 C17.13 5.88, 13.94 3.11, 9.74 -0.54" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M19.75 8.64 C19.75 9.14, 19.7 9.65, 19.6 10.14 C19.5 10.63, 19.35 11.13, 19.15 11.6 C18.96 12.07, 18.71 12.53, 18.43 12.96 C18.14 13.39, 17.81 13.81, 17.44 14.19 C17.07 14.58, 16.66 14.94, 16.22 15.26 C15.78 15.58, 15.31 15.87, 14.81 16.12 C14.32 16.37, 13.79 16.59, 13.25 16.76 C12.72 16.93, 12.15 17.06, 11.59 17.15 C11.03 17.24, 10.45 17.28, 9.88 17.28 C9.3 17.28, 8.72 17.24, 8.16 17.15 C7.6 17.06, 7.03 16.93, 6.5 16.76 C5.96 16.59, 5.43 16.37, 4.94 16.12 C4.44 15.87, 3.97 15.58, 3.53 15.26 C3.09 14.94, 2.68 14.58, 2.31 14.19 C1.94 13.81, 1.61 13.39, 1.32 12.96 C1.04 12.53, 0.79 12.07, 0.6 11.6 C0.4 11.13, 0.25 10.63, 0.15 10.14 C0.05 9.65, 0 9.14, 0 8.64 C0 8.14, 0.05 7.63, 0.15 7.14 C0.25 6.65, 0.4 6.16, 0.6 5.69 C0.79 5.22, 1.04 4.75, 1.32 4.32 C1.61 3.89, 1.94 3.47, 2.31 3.09 C2.68 2.7, 3.09 2.34, 3.53 2.02 C3.97 1.7, 4.44 1.41, 4.94 1.16 C5.43 0.91, 5.96 0.69, 6.5 0.52 C7.03 0.35, 7.6 0.22, 8.16 0.13 C8.72 0.04, 9.3 0, 9.88 0 C10.45 0, 11.03 0.04, 11.59 0.13 C12.15 0.22, 12.72 0.35, 13.25 0.52 C13.79 0.69, 14.32 0.91, 14.81 1.16 C15.31 1.41, 15.78 1.7, 16.22 2.02 C16.66 2.34, 17.07 2.7, 17.44 3.09 C17.81 3.47, 18.14 3.89, 18.43 4.32 C18.71 4.75, 18.96 5.22, 19.15 5.69 C19.35 6.16, 19.5 6.65, 19.6 7.14 C19.7 7.63, 19.73 8.39, 19.75 8.64 C19.78 8.89, 19.78 8.39, 19.75 8.64" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round"><g transform="translate(31.01057830181867 164.8085741503018) rotate(0 21.90843989373377 -18.494048425191174)" fill-rule="evenodd"><path d="M11.93 -33.36 C11.93 -33.36, 11.93 -33.36, 11.93 -33.36 M11.93 -33.36 C11.93 -33.36, 11.93 -33.36, 11.93 -33.36 M6.81 -15.28 C10.73 -19.78, 14.64 -24.29, 25.18 -36.41 M6.81 -15.28 C13.83 -23.35, 20.84 -31.42, 25.18 -36.41 M2.35 2.04 C13.52 -10.81, 24.69 -23.66, 31.87 -31.92 M2.35 2.04 C10.88 -7.77, 19.41 -17.58, 31.87 -31.92 M12.98 2.01 C18.19 -3.99, 23.41 -9.99, 37.25 -25.92 M12.98 2.01 C20.13 -6.21, 27.28 -14.44, 37.25 -25.92 M23.61 1.97 C28.01 -3.09, 32.42 -8.16, 41.32 -18.4 M23.61 1.97 C30.52 -5.98, 37.44 -13.93, 41.32 -18.4 M34.9 1.19 C38.82 -3.33, 42.75 -7.85, 46.05 -11.64 M34.9 1.19 C39.31 -3.89, 43.73 -8.97, 46.05 -11.64 M0 0 C0 0, 0 0, 0 0 M0 0 C0 0, 0 0, 0 0 M12.04 -0.13 C8.29 -3.39, 4.55 -6.65, 1.47 -9.32 M12.04 -0.13 C9.05 -2.73, 6.06 -5.33, 1.47 -9.32 M24.08 -0.27 C19.22 -4.49, 14.36 -8.72, 2.95 -18.64 M24.08 -0.27 C15.87 -7.4, 7.67 -14.54, 2.95 -18.64 M34.61 -1.71 C23.59 -11.29, 12.57 -20.87, 5.93 -26.64 M34.61 -1.71 C26.15 -9.06, 17.7 -16.42, 5.93 -26.64 M43.64 -4.47 C34.21 -12.66, 24.79 -20.85, 11.18 -32.68 M43.64 -4.47 C32.66 -14.01, 21.68 -23.55, 11.18 -32.68 M42.85 -15.76 C34.22 -23.25, 25.6 -30.75, 17.19 -38.06 M42.85 -15.76 C37.38 -20.5, 31.92 -25.25, 17.19 -38.06" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C0.78 -4.11, 1.34 -18.46, 4.68 -24.67 C8.03 -30.87, 14.94 -36.78, 20.07 -37.23 C25.2 -37.68, 31.83 -33.14, 35.45 -27.36 C39.07 -21.58, 47.71 -7.12, 41.81 -2.56 C35.9 2, 6.97 -0.43, 0 0 M0 0 C0.78 -4.11, 1.34 -18.46, 4.68 -24.67 C8.03 -30.87, 14.94 -36.78, 20.07 -37.23 C25.2 -37.68, 31.83 -33.14, 35.45 -27.36 C39.07 -21.58, 47.71 -7.12, 41.81 -2.56 C35.9 2, 6.97 -0.43, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round" transform="translate(41.4967004526286 108.23406283046478) rotate(0 10.702336545928915 9.364544477687808)"><path d="M2.43 3.43 C2.43 3.43, 2.43 3.43, 2.43 3.43 M2.43 3.43 C2.43 3.43, 2.43 3.43, 2.43 3.43 M2.56 15.48 C5.21 12.43, 7.86 9.38, 15.02 1.14 M2.56 15.48 C7.11 10.24, 11.67 5, 15.02 1.14 M9.91 19.21 C13.96 14.55, 18.01 9.9, 21.06 6.38 M9.91 19.21 C13.95 14.57, 17.98 9.93, 21.06 6.38 M4.02 16.71 C4.02 16.71, 4.02 16.71, 4.02 16.71 M4.02 16.71 C4.02 16.71, 4.02 16.71, 4.02 16.71 M16.82 17.23 C12.86 13.79, 8.9 10.35, 1.72 4.11 M16.82 17.23 C11.29 12.43, 5.77 7.63, 1.72 4.11 M21.31 10.54 C17.9 7.58, 14.49 4.61, 9.24 0.04 M21.31 10.54 C16.98 6.77, 12.64 3.01, 9.24 0.04" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M21.4 9.36 C21.4 9.91, 21.35 10.46, 21.24 10.99 C21.13 11.52, 20.97 12.06, 20.76 12.57 C20.55 13.08, 20.28 13.58, 19.97 14.05 C19.66 14.52, 19.3 14.97, 18.9 15.38 C18.5 15.8, 18.06 16.19, 17.58 16.54 C17.11 16.89, 16.59 17.2, 16.05 17.47 C15.52 17.75, 14.94 17.98, 14.36 18.16 C13.78 18.35, 13.17 18.49, 12.56 18.59 C11.95 18.68, 11.32 18.73, 10.7 18.73 C10.08 18.73, 9.45 18.68, 8.84 18.59 C8.23 18.49, 7.62 18.35, 7.04 18.16 C6.46 17.98, 5.89 17.75, 5.35 17.47 C4.81 17.2, 4.3 16.89, 3.82 16.54 C3.35 16.19, 2.9 15.8, 2.5 15.38 C2.11 14.97, 1.74 14.52, 1.43 14.05 C1.12 13.58, 0.86 13.08, 0.65 12.57 C0.43 12.06, 0.27 11.52, 0.16 10.99 C0.06 10.46, 0 9.91, 0 9.36 C0 8.82, 0.06 8.27, 0.16 7.74 C0.27 7.2, 0.43 6.67, 0.65 6.16 C0.86 5.65, 1.12 5.15, 1.43 4.68 C1.74 4.21, 2.11 3.76, 2.5 3.35 C2.9 2.93, 3.35 2.54, 3.82 2.19 C4.3 1.84, 4.81 1.53, 5.35 1.25 C5.89 0.98, 6.46 0.75, 7.04 0.56 C7.62 0.38, 8.23 0.24, 8.84 0.14 C9.45 0.05, 10.08 0, 10.7 0 C11.32 0, 11.95 0.05, 12.56 0.14 C13.17 0.24, 13.78 0.38, 14.36 0.56 C14.94 0.75, 15.52 0.98, 16.05 1.25 C16.59 1.53, 17.11 1.84, 17.58 2.19 C18.06 2.54, 18.5 2.93, 18.9 3.35 C19.3 3.76, 19.66 4.21, 19.97 4.68 C20.28 5.15, 20.55 5.65, 20.76 6.16 C20.97 6.67, 21.13 7.2, 21.24 7.74 C21.35 8.27, 21.38 9.09, 21.4 9.36 C21.43 9.64, 21.43 9.09, 21.4 9.36" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round"><g transform="translate(60.16191375626954 131.13950946524886) rotate(0 16.71865860152218 9.921154001040179)" fill-rule="evenodd"><path d="M0 0 C0 0, 0 0, 0 0 M0 0 C0 0, 0 0, 0 0 M6.04 5.25 C9.16 1.65, 12.29 -1.95, 17.85 -8.34 M6.04 5.25 C10.25 0.4, 14.46 -4.44, 17.85 -8.34 M12.08 10.5 C15.01 7.13, 17.94 3.75, 25.2 -4.6 M12.08 10.5 C14.97 7.17, 17.86 3.84, 25.2 -4.6 M15.49 18.76 C19.46 14.19, 23.44 9.62, 31.23 0.65 M15.49 18.76 C19.67 13.96, 23.85 9.15, 31.23 0.65 M16.93 29.3 C21.06 24.55, 25.19 19.8, 33.34 10.43 M16.93 29.3 C20.79 24.86, 24.64 20.43, 33.34 10.43 M29.53 27 C30.67 25.69, 31.81 24.38, 34.78 20.96 M29.53 27 C31.37 24.88, 33.21 22.77, 34.78 20.96 M14.43 27.6 C14.43 27.6, 14.43 27.6, 14.43 27.6 M14.43 27.6 C14.43 27.6, 14.43 27.6, 14.43 27.6 M25.72 26.82 C23.22 24.65, 20.73 22.48, 16.66 18.94 M25.72 26.82 C23.72 25.08, 21.73 23.35, 16.66 18.94 M33.98 23.4 C23.4 14.21, 12.83 5.01, 3.04 -3.5 M33.98 23.4 C26.2 16.64, 18.42 9.87, 3.04 -3.5 M36.97 15.4 C26.72 6.49, 16.47 -2.42, 9.8 -8.22 M36.97 15.4 C30.82 10.05, 24.67 4.71, 9.8 -8.22" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C0.86 -0.93, 3.58 -4.18, 5.17 -5.57 C6.77 -6.97, 7.56 -7.83, 9.55 -8.36 C11.54 -8.89, 14.99 -8.89, 17.12 -8.76 C19.24 -8.62, 20.83 -8.43, 22.29 -7.56 C23.75 -6.7, 24.88 -5.11, 25.87 -3.58 C26.87 -2.06, 27.47 -0.33, 28.26 1.59 C29.06 3.52, 29.92 5.84, 30.65 7.96 C31.38 10.08, 32.18 12.41, 32.64 14.33 C33.11 16.25, 33.44 17.78, 33.44 19.51 C33.44 21.23, 33.3 23.42, 32.64 24.68 C31.98 25.94, 30.72 26.47, 29.46 27.07 C28.2 27.67, 26.87 28, 25.08 28.26 C23.29 28.53, 20.43 28.73, 18.71 28.66 C16.98 28.59, 15.46 28.93, 14.73 27.86 C14 26.8, 14.66 23.82, 14.33 22.29 C14 20.77, 13.47 20.23, 12.74 18.71 C12.01 17.18, 11.08 15.33, 9.95 13.14 C8.82 10.95, 7.63 7.76, 5.97 5.57 C4.31 3.38, 1 0.93, 0 0 M0 0 C0.86 -0.93, 3.58 -4.18, 5.17 -5.57 C6.77 -6.97, 7.56 -7.83, 9.55 -8.36 C11.54 -8.89, 14.99 -8.89, 17.12 -8.76 C19.24 -8.62, 20.83 -8.43, 22.29 -7.56 C23.75 -6.7, 24.88 -5.11, 25.87 -3.58 C26.87 -2.06, 27.47 -0.33, 28.26 1.59 C29.06 3.52, 29.92 5.84, 30.65 7.96 C31.38 10.08, 32.18 12.41, 32.64 14.33 C33.11 16.25, 33.44 17.78, 33.44 19.51 C33.44 21.23, 33.3 23.42, 32.64 24.68 C31.98 25.94, 30.72 26.47, 29.46 27.07 C28.2 27.67, 26.87 28, 25.08 28.26 C23.29 28.53, 20.43 28.73, 18.71 28.66 C16.98 28.59, 15.46 28.93, 14.73 27.86 C14 26.8, 14.66 23.82, 14.33 22.29 C14 20.77, 13.47 20.23, 12.74 18.71 C12.01 17.18, 11.08 15.33, 9.95 13.14 C8.82 10.95, 7.63 7.76, 5.97 5.57 C4.31 3.38, 1 0.93, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(42.24312730293559 131.12763356184445) rotate(0 -16.121563651467795 12.193947400441964)" fill-rule="evenodd"><path d="M-24.42 -2.68 C-24.42 -2.68, -24.42 -2.68, -24.42 -2.68 M-24.42 -2.68 C-24.42 -2.68, -24.42 -2.68, -24.42 -2.68 M-26.26 11.62 C-22.63 7.45, -19 3.27, -12.48 -4.23 M-26.26 11.62 C-22.27 7.03, -18.28 2.44, -12.48 -4.23 M-29.41 27.44 C-22.35 19.32, -15.29 11.2, -2.51 -3.51 M-29.41 27.44 C-19.56 16.11, -9.71 4.78, -2.51 -3.51 M-22.71 31.93 C-18.64 27.24, -14.56 22.56, -8.28 15.33 M-22.71 31.93 C-17.53 25.97, -12.35 20.01, -8.28 15.33 M-12.74 32.65 C-12.15 31.98, -11.57 31.3, -10.77 30.39 M-12.74 32.65 C-12.23 32.07, -11.73 31.49, -10.77 30.39 M-31.63 25.72 C-31.63 25.72, -31.63 25.72, -31.63 25.72 M-31.63 25.72 C-31.63 25.72, -31.63 25.72, -31.63 25.72 M-13.55 30.83 C-17.43 27.46, -21.3 24.09, -29.4 17.05 M-13.55 30.83 C-19.26 25.87, -24.96 20.91, -29.4 17.05 M-6.79 26.11 C-12.88 20.81, -18.98 15.52, -27.92 7.74 M-6.79 26.11 C-13.07 20.65, -19.34 15.2, -27.92 7.74 M-8.34 14.16 C-11.82 11.14, -15.3 8.11, -24.94 -0.27 M-8.34 14.16 C-12.4 10.63, -16.47 7.09, -24.94 -0.27 M-4.6 6.81 C-9.6 2.47, -14.6 -1.88, -20.45 -6.96 M-4.6 6.81 C-9 2.98, -13.41 -0.85, -20.45 -6.96 M-0.1 0.12 C-4.38 -3.6, -8.66 -7.32, -12.93 -11.03 M-0.1 0.12 C-2.96 -2.36, -5.81 -4.84, -12.93 -11.03" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C-0.66 -0.73, -2.59 -3.18, -3.98 -4.38 C-5.37 -5.57, -6.37 -6.63, -8.36 -7.17 C-10.35 -7.7, -13.8 -7.7, -15.92 -7.56 C-18.05 -7.43, -19.64 -7.23, -21.1 -6.37 C-22.56 -5.51, -23.68 -3.91, -24.68 -2.39 C-25.68 -0.86, -26.27 0.86, -27.07 2.79 C-27.86 4.71, -28.73 7.03, -29.46 9.16 C-30.19 11.28, -30.98 13.6, -31.45 15.52 C-31.91 17.45, -32.24 18.97, -32.24 20.7 C-32.24 22.42, -32.11 24.61, -31.45 25.87 C-30.78 27.13, -29.46 27.53, -28.26 28.26 C-27.07 28.99, -26.01 29.72, -24.28 30.25 C-22.56 30.78, -20.1 31.25, -17.91 31.45 C-15.72 31.65, -12.41 32.64, -11.15 31.45 C-9.89 30.25, -10.62 26.07, -10.35 24.28 C-10.08 22.49, -9.89 22.29, -9.55 20.7 C-9.22 19.11, -9.16 17.05, -8.36 14.73 C-7.56 12.41, -6.17 9.22, -4.78 6.77 C-3.38 4.31, -0.8 1.13, 0 0 M0 0 C-0.66 -0.73, -2.59 -3.18, -3.98 -4.38 C-5.37 -5.57, -6.37 -6.63, -8.36 -7.17 C-10.35 -7.7, -13.8 -7.7, -15.92 -7.56 C-18.05 -7.43, -19.64 -7.23, -21.1 -6.37 C-22.56 -5.51, -23.68 -3.91, -24.68 -2.39 C-25.68 -0.86, -26.27 0.86, -27.07 2.79 C-27.86 4.71, -28.73 7.03, -29.46 9.16 C-30.19 11.28, -30.98 13.6, -31.45 15.52 C-31.91 17.45, -32.24 18.97, -32.24 20.7 C-32.24 22.42, -32.11 24.61, -31.45 25.87 C-30.78 27.13, -29.46 27.53, -28.26 28.26 C-27.07 28.99, -26.01 29.72, -24.28 30.25 C-22.56 30.78, -20.1 31.25, -17.91 31.45 C-15.72 31.65, -12.41 32.64, -11.15 31.45 C-9.89 30.25, -10.62 26.07, -10.35 24.28 C-10.08 22.49, -9.89 22.29, -9.55 20.7 C-9.22 19.11, -9.16 17.05, -8.36 14.73 C-7.56 12.41, -6.17 9.22, -4.78 6.77 C-3.38 4.31, -0.8 1.13, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(109.94583739107611 136.19561989081518) rotate(0 69.86077098192868 -0.628256155844543)"><path d="M0.76 -0.52 C23.9 -0.9, 116.79 -1.11, 140.02 -1.1 M-0.3 1.82 C22.6 1.56, 115.87 -2.38, 139.18 -3.07" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(109.94583739107611 136.19561989081518) rotate(0 69.86077098192868 -0.628256155844543)"><path d="M110.51 8.53 C122.8 4.08, 134.88 -1.74, 138.37 -1.87 M111.7 8.58 C118.29 5.18, 126.07 2.75, 138.3 -4.02" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(109.94583739107611 136.19561989081518) rotate(0 69.86077098192868 -0.628256155844543)"><path d="M109.76 -11.98 C122.55 -8.28, 134.93 -5.94, 138.37 -1.87 M110.95 -11.93 C117.82 -9.77, 125.79 -6.67, 138.3 -4.02" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(349.4528943119219 141.58654175254128) rotate(0 97.18164883703821 -0.7118767047838226)"><path d="M0.19 0.29 C32.65 0.36, 163.1 0.21, 195.53 -0.08 M-1.16 -0.61 C31.1 -0.82, 162.27 -1.76, 194.75 -1.73" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(349.4528943119219 141.58654175254128) rotate(0 97.18164883703821 -0.7118767047838226)"><path d="M167.07 9.17 C178.37 4.03, 186.29 2.26, 194.15 -1.07 M166.04 8.4 C172.04 6.78, 177.25 3.33, 194.33 -1.72" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(349.4528943119219 141.58654175254128) rotate(0 97.18164883703821 -0.7118767047838226)"><path d="M167 -11.35 C178.23 -9.03, 186.18 -3.35, 194.15 -1.07 M165.96 -12.12 C172.05 -9.53, 177.27 -8.76, 194.33 -1.72" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(352.2217620219892 90.64891427363261) rotate(0 94.69918799397601 -23.79390688422322)"><path d="M0.72 -0.36 C32.25 -8.15, 157.35 -39.68, 188.68 -47.23" stroke="#000000" stroke-width="1.5" fill="none" stroke-dasharray="8 9"></path></g><g transform="translate(352.2217620219892 90.64891427363261) rotate(0 94.69918799397601 -23.79390688422322)"><path d="M163.18 -29.85 C168.43 -34.36, 177.55 -40.48, 188.2 -47.83" stroke="#000000" stroke-width="1.5" fill="none"></path></g><g transform="translate(352.2217620219892 90.64891427363261) rotate(0 94.69918799397601 -23.79390688422322)"><path d="M158.25 -49.77 C164.71 -49.13, 175.11 -50.06, 188.2 -47.83" stroke="#000000" stroke-width="1.5" fill="none"></path></g></g><mask></mask><g transform="translate(355.64421201976756 33.634031146009704) rotate(344.9033703822942 75.51600646972656 7.65143055727205)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="12.24228889163527px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">switch traffic when ready</text></g><g stroke-linecap="round"><g transform="translate(550.227658707631 76.9681642912675) rotate(0 0.4614221589972658 70.95185539230519)"><path d="M-0.16 0.1 C-0.25 23.51, 0.02 117.7, 0.42 141.24 M-1.7 -0.89 C-1.5 22.65, 2.01 118.85, 2.62 142.8" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(548.8432248525971 76.9681642912675) rotate(0 23.259719931793143 -0.9142844041955271)"><path d="M-0.32 0.45 C7.51 0.25, 38.94 -0.42, 46.84 -0.58 M1.72 -0.35 C9.37 -0.95, 38.34 -1.94, 45.76 -2.28" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(548.8432248525971 218.18041750471411) rotate(0 31.250096698352195 -1.775462741694696)"><path d="M1.08 -0.37 C11.33 -1.06, 52.29 -2.87, 62.31 -3.18 M0.19 -1.61 C10.2 -2.21, 50.82 -1.41, 61.37 -1.86" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g transform="translate(745.4328322673953 17.43750852481452) rotate(0 139.8900146484375 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Upgrade one node at a time</text></g></svg>
\ No newline at end of file
diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index fdbdbe03a7..343c048a9c 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -46,10 +46,9 @@ You might want to delay upgrading in the following situations:
 You can stay informed about new FusionAuth releases and updates by:
 
 . Monitoring the link:/docs/v1/tech/release-notes[release notes]
-. Subscribing to the FusionAuth newsletter
-. Following FusionAuth on social media platforms
-. Monitoring the FusionAuth GitHub repository
-. Participating in the FusionAuth community forum
+. Join the https://fusionauth.io/community[FusionAuth Community site] and https://fusionauth.slack.com/join/shared_invite/zt-6ykfov9u-MTwA1A6ptv0Gr6KcFBVG4w#/shared-invite/email[Slack channel]
+. Following FusionAuth on social media platforms, including https://twitter.com/FusionAuth[Twitter] and https://www.linkedin.com/company/fusionauth[LinkedIn].
+. Monitoring the https://github.com/FusionAuth/[FusionAuth GitHub repository]
 
 == How to Think About Upgrades
 
@@ -58,6 +57,8 @@ Before upgrading FusionAuth, consider the following:
 . Read the link:/docs/v1/tech/release-notes[release notes].  Release notes help you understand if an update affects you. They include details on new features, improvements, bug fixes, and potential breaking changes.
 . Test the upgrade in a staging or development environment to identify potential issues
 . Plan for any downtime or maintenance windows required for the upgrade. If there are changes to the database schema required, this could require more steps and downtime than a pure application upgrade. 
+. FusionAuth can perform database migrations automatically and silently, interactively, or you can run any needed scripts yourself. With any method, you should perform a manual backup of your database before upgrading.
+. Consider that a FusionAuth server upgrade might mean that you need to upgrade your client libraries as well. Check before upgrading if this is needed, as it will entail a more complex upgrade process, and may require more downtime.
 . Review custom themes, client libraries, and configuration settings for compatibility with the new version
 . Consider using blue/green deployments or rolling upgrades to minimize downtime
 
@@ -65,31 +66,60 @@ Before upgrading FusionAuth, consider the following:
 
 === Easiest Route
 
-The easiest route with the least pre-planning and logistics is to simply stop all your services, upgrade everything, and then bring it all back online. 
+The easiest upgrade route is to simply stop all your services, upgrade everything, and then bring it all back online. 
 
-The disadvantage of this is that your site will experience a full outage. This may be acceptable for many use cases eg. internal systems that are only used during office hours, or a website that is only used during certain hours in a particular timezone. 
+This is a good option for single instance development or QA systems, or for systems that can tolerate downtime.
 
-If downtime is not an option then rolling upgrades, or a blue/green deployment might be more suitable. 
+If minimizing downtime is a goal, then rolling upgrades, or a blue/green deployment might be more suitable. 
 
 == Rolling Upgrade
 
+You can perform a rolling upgrade if you have 3 FusionAuth nodes running behind a load balancer. Each node is upgraded one at a time, and the load balancer is configured to direct traffic to the upgraded nodes as they become available for use. This allows you to upgrade FusionAuth with minimal downtime. 
+
+Because individual nodes are taken offline during the rolling update, the capacity of your installation is reduced during the upgrade.
+
+You can choose to run in-place upgrades on each node, or to replace each node with a new node running the latest version of FusionAuth. In place upgrades are potentially faster, but if something goes wrong, you may need to roll back the upgrade. Replacing nodes may be slower, but if something goes wrong, you can simply revert to the previous version of FusionAuth by pointing the load balancer to the old nodes.
+
+A procedure might look like this:
+- Stop the first node, and remove it from the load balancer
+- Upgrade FusionAuth on first node. After FusionAuth is update, you can start it up, so that it can perform the database migrations. This will lock the database, and own it while it completes the database upgrade. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may error while the first node is being upgraded.
+- Start the first node, and add it back to the load balancer
+- Stop the second and third nodes, and remove them from the load balancer, and upgrade them. 
+- Start the second and third nodes, and add them back to the load balancer
+
+This way there is still some downtime, but it is limited to the time it takes to run the database migration on the upgraded first node. There will be limited capacity during the upgrade, especially while the second and third nodes are upgrading, but the system will be available for use for the majority of the upgrade process.
+
+To maximize available capacity during the upgrade, 
 
 === Blue / Green Deployment
 
+A blue / green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue / green deployment instead of performing a rolling upgrade completely isolates the upgrade process from the production environment, reducing impact and risk to the current production environment.
+
+To perform a blue/green deployment with a 3 node cluster, first create 3 entirely new nodes. Add one of these nodes to the existing cluster. At this point, the new node will lock the database, and own it while it completes the database upgrade. The original nodes might start to error - they can be removed. The remaining new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
+ 
 === Out of Band Database Upgrades
 
+
+
 == FAQs
 
-Q: What is runtime mode and how does that affect upgrades
-Q: What is maintenance mode
-Q: What silent mode means
+Q: What is runtime mode and how does that affect upgrades?
+A: FusionAuth's Runtime mode can either be 'production' or "development". When in the `development`` runtime mode, maintenance mode will interactively assist you configuring the database and connecting to Elasticsearch if configured. Once you move FusionAuth into production, it is recommended that you modify the runtime mode to `production`. When in production runtime mode maintenance mode will no longer be available to you which means you can be certain that your end users will not find themselves on the database upgrade panel during an Upgrade. When in production mode you will either need to leverage Silent Mode to automatically apply database migrations or you will need to apply the database migrations yourself (either by hand or via a script of some sort).For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide] for reference.
+
+Q: What is Maintenance Mode?
+A: Maintenance Mode is a special admin interface for FusionAuth, which is helpful to interactively upgrade FusionAuth or setup database connections. You can switch to Maintenance mode by switching to the `development` runtime mode, and setting Silent Mode to false. 
+
+Q: What is Silent Mode?
+A: link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments, or for when you want to upgrade FusionAuth without using the Maintenance Mode interface. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in `production` runtime mode as well. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will switch to the manual Maintenance Mode interface.
+
 Q: How many versions can I skip?
-A: We recommended migrating from one minor version to the next over
+A: We recommended migrating from one minor version to the next over. 
 
 Q: How often should I upgrade?
-A: You can upgrade whenever you want. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release. In addition, we don't typically backport bug fixes. so if you run into an issue, you'll need to upgrade to get the fix
-Q: How can I find out about new releases
+A: You can upgrade whenever you want. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release. In addition, we don't typically backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix.
 
+Q: How can I find out about new releases?
+A: We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. 
 
 
 [NOTE]
@@ -309,11 +339,10 @@ For more information on the various configuration options, see the link:/docs/v1
 
 [NOTE]
 ====
-You should always backup your database prior to using Maintenance Mode.
+You should always backup your database prior to upgrading using Maintenance Mode.
 ====
 
-Depending on your current version and the new version you will be updating to you might need to execute one or more SQL scripts to update your
- database. These scripts are located in the migrations folder inside the Database Schema ZIP file. This file can be downloaded by finding the database zip on the https://fusionauth.io/direct-download[Direct Downloads] page.
+Depending on your current version and the new version you will be updating to you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder inside the Database Schema ZIP file. This file can be downloaded by finding the database zip on the https://fusionauth.io/direct-download[Direct Downloads] page.
 
 [WARNING]
 ====

From fb5e355ee0354cb3e67ecf85d53ce7f39c4a372c Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Tue, 9 May 2023 10:17:21 +0200
Subject: [PATCH 07/55] added around versions and configs

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 53 ++++++++++++++++++----
 1 file changed, 43 insertions(+), 10 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 343c048a9c..8e5b2d38e6 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -52,15 +52,48 @@ You can stay informed about new FusionAuth releases and updates by:
 
 == How to Think About Upgrades
 
-Before upgrading FusionAuth, consider the following:
+Before upgrading FusionAuth, there are a number of things to consider. Go through each of the points below to see if any of them apply to your situation.
 
-. Read the link:/docs/v1/tech/release-notes[release notes].  Release notes help you understand if an update affects you. They include details on new features, improvements, bug fixes, and potential breaking changes.
-. Test the upgrade in a staging or development environment to identify potential issues
-. Plan for any downtime or maintenance windows required for the upgrade. If there are changes to the database schema required, this could require more steps and downtime than a pure application upgrade. 
-. FusionAuth can perform database migrations automatically and silently, interactively, or you can run any needed scripts yourself. With any method, you should perform a manual backup of your database before upgrading.
-. Consider that a FusionAuth server upgrade might mean that you need to upgrade your client libraries as well. Check before upgrading if this is needed, as it will entail a more complex upgrade process, and may require more downtime.
-. Review custom themes, client libraries, and configuration settings for compatibility with the new version
-. Consider using blue/green deployments or rolling upgrades to minimize downtime
+=== Update Contents and Notes
+
+Read the link:/docs/v1/tech/release-notes[release notes].  Release notes help you understand if an update affects you. They include details on new features, improvements, bug fixes, and potential breaking changes.
+
+=== Testing
+
+Before starting the upgrade process on production, test the upgrade in a staging or development environment to identify potential issues. This is particularly important on more complex upgrades involving multiple version jumps, or if you have made customizations to FusionAuth.
+
+=== Downtime and Database Migrations
+
+Plan for any downtime or maintenance windows required for the upgrade. If changes to the database schema are required, this could require more steps and downtime that affects end users. A pure application upgrade on the other hand may only affect admin functionality, and not require any downtime from an end user perspective.
+
+FusionAuth can perform database migrations automatically and silently using called link:/docs/v1/tech/guides/silent-mode[Silent Mode]. 
+
+If you want to interactively (called link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode]), or you can run any needed scripts out of band (meaning directly on the database yourself). With any method, you should perform a backup of your database before upgrading.
+
+The timing of the database upgrade is also important to note. When an upgraded node is added to a FusionAuth cluster, it will lock the database and perform the database upgrade if configured for Silent Mode. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. 
+
+=== Connected Applications and Client Libraries
+
+Consider that a FusionAuth server upgrade might mean that you need to upgrade your client libraries as well. Check before upgrading if this is needed, as it will entail a more complex upgrade process, and may require more downtime.
+
+=== Skipping Versions 
+
+Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. This is called a "version jump". FusionAuth migration can run all the necessary database migrations to get you to the latest version. However, we recommend that you don't skip minor versions, and rather migrate from one minor version to the next, step by step. For example, if you want to get to version 1.43, and you are on version 1.37, we recommend that you upgrade to each minor step to 1.43.
+
+=== Migrating Configuration between Environments
+
+There are a number of options you can use to manage the configuration of your FusionAuth instance over time, as well as to promote changes from one environment. These include:
+
+- Script The Changes
+- Terraform
+- Pulumi
+- Manual Configuration via the UI
+
+You can read more at link:/docs/v1/tech/admin-guide/configuration-management[the Configuration Management guide].
+
+=== Themes and Customizations
+
+Review custom themes. If you have made any customizations, you may need to update them to work with the new version of FusionAuth. You can use the https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] project to perform diffs on the themes to identify any changes that need to be made.
 
 == Upgrade Options
 
@@ -68,11 +101,11 @@ Before upgrading FusionAuth, consider the following:
 
 The easiest upgrade route is to simply stop all your services, upgrade everything, and then bring it all back online. 
 
-This is a good option for single instance development or QA systems, or for systems that can tolerate downtime.
+This is a good option for single instance development or QA systems, or for systems that can tolerate longer amounts of downtime.
 
 If minimizing downtime is a goal, then rolling upgrades, or a blue/green deployment might be more suitable. 
 
-== Rolling Upgrade
+=== Rolling Upgrade
 
 You can perform a rolling upgrade if you have 3 FusionAuth nodes running behind a load balancer. Each node is upgraded one at a time, and the load balancer is configured to direct traffic to the upgraded nodes as they become available for use. This allows you to upgrade FusionAuth with minimal downtime. 
 

From 03c4b40de064d56165807023859ffb9d257e969d Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Wed, 10 May 2023 12:51:15 +0200
Subject: [PATCH 08/55] updated index and added images

---
 .../docs/v1/tech/admin-guide/upgrade-new.adoc |   5 +
 site/docs/v1/tech/admin-guide/upgrade.adoc    | 135 ++++++++++++++----
 2 files changed, 116 insertions(+), 24 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade-new.adoc b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
index 0eefe108fc..8b55142da8 100644
--- a/site/docs/v1/tech/admin-guide/upgrade-new.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
@@ -8,10 +8,15 @@ Second, how to think about upgrades:
 Read the release notes. How do I tell if something affects me?
 How do I upgrade my custom theme (need to document how to do a diff of theme changes across versions, maybe even start a project that does that--pulls down the default theme from each released version of FusionAuth and commits it to a GH repo, perhaps part of this: https://github.com/FusionAuth/fusionauth-theme-helper )
 How do I migrate FusionAuth config changes between environments (pointing to/extracting content from this https://fusionauth.io/docs/v1/tech/admin-guide/configuration-management )
+
 How can I upgrade my database with minimal downtime?
+
 How do I switch out nodes if running in a cluster? What happens when the first node is switched out (it checks for the correct schema and upgrades if needed).
+
 How to handle main use cases: in dev envt, in docker/kubernetes, in cluster.
+
 Should I upgrade from 1.37 -> 1.43 jumping versions or step by step?
+
 How can customer know if upgrade will cause downtime? Can they use a staging envrionment to do so? If db migration is shown, yes, otherwise maybe? are there dev team todos to make this clearer? Can we talk about durations for a reference architecture. 
 
 Differentiate between an upgrade that has downtime around admin functionality and upgrade that affects end user login functionality (the old control plane/data plane metaphor)
diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 8e5b2d38e6..265d40a0d5 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -7,21 +7,34 @@ navcategory: admin
 
 == Upgrading
 
-In order to upgrade FusionAuth to a later version use the following guides. Below you will find steps to follow if you are using `.deb` or `.rpm` package on Linux, or a `.zip` package on macOS, Linux or Windows.
+In order to upgrade FusionAuth to a later version, there are a number of things to consider. This document will help you understand the upgrade process, and how to plan for it. It also covers detailed instructions on how to upgrade FusionAuth on various platforms and distributions.
 
 Topics covered in this document:
 
 * <<When to Upgrade>>
+** <<Reasons to Upgrade>>
+** <<Reasons Not to Upgrade>>
+** <<Being Aware of Upgrade Options>>
 * <<Thinking About Upgrades>>
+** <<Update Contents and Notes>>
+** <<Testing>>
+** <<Downtime and Database Migrations>>
+** <<Connected Applications and Client Libraries>>
+** <<Skipping Versions>>
+** <<Migrating Configuration between Environments>>
+** <<Themes and Customizations>>
+* <<Upgrade Options>>
+** <<Easiest Route>>
+** <<Rolling Upgrade>>
+** <<Blue/Green Deployment>>
+** <<Out of Band Database Upgrades>>
+* <<FAQs>>
+* <<Detailed Upgrade Instructions>>
 * <<ZIP Packages>>
 * <<Linux Packages>>
 ** <<Troubleshooting Upgrade with RPMs>>
 * <<FastPath>>
 * <<Database>>
-* <<Themes>>
-* <<Downtime>>
-
-If you used the FastPath or other installation methods initially, you may prefer to use that same mode to download the latest version of FusionAuth. If you would like to continue by manually downloading the necessary packages, read on.
 
 == When to Upgrade
 
@@ -68,7 +81,12 @@ Plan for any downtime or maintenance windows required for the upgrade. If change
 
 FusionAuth can perform database migrations automatically and silently using called link:/docs/v1/tech/guides/silent-mode[Silent Mode]. 
 
-If you want to interactively (called link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode]), or you can run any needed scripts out of band (meaning directly on the database yourself). With any method, you should perform a backup of your database before upgrading.
+If you want to interactively (called link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode]), or you can run any needed scripts out of band (meaning directly on the database yourself). 
+
+[NOTE]
+====
+You should always backup your database prior to using Maintenance Mode, or performing any database migrations by any method.
+====.
 
 The timing of the database upgrade is also important to note. When an upgraded node is added to a FusionAuth cluster, it will lock the database and perform the database upgrade if configured for Silent Mode. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. 
 
@@ -93,7 +111,9 @@ You can read more at link:/docs/v1/tech/admin-guide/configuration-management[the
 
 === Themes and Customizations
 
-Review custom themes. If you have made any customizations, you may need to update them to work with the new version of FusionAuth. You can use the https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] project to perform diffs on the themes to identify any changes that need to be made.
+Review custom themes and how they will be impacted by any FusionAuth updates. If you have made any customizations, you may need to update them to work with the new version of FusionAuth. You can use the https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] project to perform diffs on the themes to identify any changes that need to be made.
+
+include::docs/v1/tech/installation-guide/_theme-upgrade.adoc[]
 
 == Upgrade Options
 
@@ -122,16 +142,87 @@ A procedure might look like this:
 
 This way there is still some downtime, but it is limited to the time it takes to run the database migration on the upgraded first node. There will be limited capacity during the upgrade, especially while the second and third nodes are upgrading, but the system will be available for use for the majority of the upgrade process.
 
-To maximize available capacity during the upgrade, 
+{% include _image.liquid src="/assets/img/docs/admin-guide/upgrade/blue-green.svg " alt="A representation of a Rolling upgrade." class="img-fluid" figure=true %}
 
-=== Blue / Green Deployment
+=== Blue/Green Deployment
 
 A blue / green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue / green deployment instead of performing a rolling upgrade completely isolates the upgrade process from the production environment, reducing impact and risk to the current production environment.
 
-To perform a blue/green deployment with a 3 node cluster, first create 3 entirely new nodes. Add one of these nodes to the existing cluster. At this point, the new node will lock the database, and own it while it completes the database upgrade. The original nodes might start to error - they can be removed. The remaining new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
+To perform a blue/green deployment with a 3 node cluster, first create 3 entirely new nodes. Add one of these nodes to the existing cluster. At this point, the new node will lock the database, and own it while it completes the database upgrade. The original nodes might start to error, as they will not have access to the database. They can be removed. The remaining new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
+
+{% include _image.liquid src="/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg" alt="A representation of a Blue/Green upgrade." class="img-fluid" figure=true %}
  
 === Out of Band Database Upgrades
 
+While FusionAuth can handle database migrations completely automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode] or interactively using Maintenance Mode, you may want to perform the database upgrade yourself. This is useful if you want to perform the database upgrade in a way that minimizes downtime, or as part of a larger automated or coordinated deployment. The scripts for the database migrations are available in the FusionAuth upgrade packages. 
+
+Depending on your current version and the new version you will be updating to you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder inside the Database Schema ZIP file. This file can be downloaded by finding the database zip on the https://fusionauth.io/direct-download[Direct Downloads] page.
+
+[WARNING]
+====
+When upgrading your database from a previous version, be sure to only run the scripts located in the `migrations` folder, the base files
+ `mysql.sql` and `postgresql.sql` should only be used during a clean installation when no database schema is present.
+====
+
+Inside of the database schema zip file, you will find the FusionAuth migrations. Run them in order, starting with the first migration greater than the version you are coming from, and ending with the version that is less than or equal to the target upgrade version.
+
+For example, if upgrading from version `1.19.1` to `1.22.0`, run the following SQL migrations in this order:
+
+* `1.20.0.sql`
+* `1.21.0.sql`
+* `1.22.0.sql`
+
+[source]
+----
+fusionauth-database-schema/
+|-- migrations/
+    |--  [mysql | postgresql]/
+      |-- 1.1.0.sql
+      |-- 1.2.0.sql
+      |-- 1.3.0.sql
+      |-- 1.3.1.sql
+      |-- 1.5.0.sql
+      |-- 1.6.0.sql
+      |-- 1.7.0.sql
+      |-- 1.7.1.sql
+      |-- 1.8.0-RC.1.sql
+      |-- 1.8.1-RC.1.sql
+      |-- 1.11.0.sql
+      |-- 1.12.0.sql
+      |-- 1.13.0.sql
+      |-- 1.14.0.sql
+      |-- 1.15.0.sql
+      |-- 1.15.3.sql
+      |-- 1.16.0-RC.1.sql
+      |-- 1.16.0.sql
+      |-- 1.17.0.sql
+      |-- 1.17.3.sql
+      |-- 1.18.0.sql
+      |-- 1.18.2.sql
+      |-- 1.19.0.sql
+      |-- 1.20.0.sql
+      |-- 1.21.0.sql
+      |-- 1.22.0.sql
+      |-- 1.23.0.sql
+      |-- 1.25.0.sql
+      |-- 1.26.0.sql
+      |-- 1.27.0.sql
+      |-- 1.28.0.sql
+      |-- 1.28.1.sql
+      |-- 1.29.1.sql
+      |-- 1.30.0.sql
+      |-- 1.30.1.sql
+      |-- 1.30.2.sql
+      |-- 1.32.0.sql
+      |-- 1.33.0.sql
+      |-- 1.35.0.sql
+      |-- 1.36.0.sql
+      |-- 1.37.0.sql
+      |-- 1.40.1.sql
+      |-- 1.41.0.sql
+      |-- 1.43.0.sql
+      |-- 1.44.0.sql
+----
 
 
 == FAQs
@@ -155,6 +246,10 @@ Q: How can I find out about new releases?
 A: We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. 
 
 
+== Detailed Upgrade Instructions
+
+This section will guide you with detailed technical instructions on how to upgrade FusionAuth nodes on different platforms.
+
 [NOTE]
 ====
 *Readme*
@@ -169,11 +264,11 @@ If you want to use manual mode, download the latest version of FusionAuth and fo
 ====
 
 
-== ZIP Packages
+=== ZIP Packages
 
 FusionAuth is available in a zip package for macOS, Linux and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth.
 
-=== macOS and Linux
+==== macOS and Linux
 
 In this example, we'll assume you have previously installed FusionAuth in `/usr/local/fusionauth` and this directory will be referred to `FUSIONAUTH_HOME`. If you have used a different directory you can adjust the following example accordingly.
 
@@ -229,7 +324,7 @@ Finally restart the FusionAuth services.
 /usr/local/fusionauth/bin/startup.sh
 ----
 
-=== Windows
+==== Windows
 
 In this example, we'll assume you have previously installed FusionAuth in `\fusionauth` and this directory will be referred to `FUSIONAUTH_HOME`. If you have used a different directory you can adjust the following example accordingly.
 
@@ -312,7 +407,7 @@ Versions 1.37.0 through 1.39.0 do not support native Windows installation.
 
 That is it, you're done!
 
-== Linux Packages
+=== Linux Packages
 
 Updating your application is easy if you installed using the RPM or Debian packages. All you need to do is to issue an update command to the dpkg or rpm program and specify the new package file. Here is an example:
 
@@ -345,7 +440,7 @@ sudo systemctl start fusionauth-search
 sudo systemctl start fusionauth-app
 ----
 
-=== Troubleshooting Upgrade with RPMs
+==== Troubleshooting Upgrade with RPMs
 
 include::docs/v1/tech/shared/_troubleshooting-uninstall-upgrade-reinstall-rpm.adoc[]
 
@@ -355,7 +450,7 @@ While FastPath is an option to perform an upgrade, the FastPath process limits t
 
 When in a production environment please utilize `.deb` or `.rpm` packages when on Linux. If you your production platform is macOS or Windows, please manually manage the upgrade using the `.zip` bundles.
 
-== Database
+=== Database
 
 [NOTE]
 ====
@@ -442,11 +537,3 @@ fusionauth-database-schema/
       |-- 1.43.0.sql
       |-- 1.44.0.sql
 ----
-
-== Themes
-
-include::docs/v1/tech/installation-guide/_theme-upgrade.adoc[]
-
-== Downtime
-
-include::docs/v1/tech/installation-guide/_downtime-upgrade-limitation.adoc[]

From 419fabb1f456decbca4ebf609cde6838e0123d50 Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <gareth@ritza.co>
Date: Wed, 10 May 2023 13:19:15 +0200
Subject: [PATCH 09/55] remove old new guides

---
 .../docs/v1/tech/admin-guide/upgrade-new.adoc |  73 ----
 .../docs/v1/tech/admin-guide/upgrade-old.adoc | 319 ------------------
 2 files changed, 392 deletions(-)
 delete mode 100644 site/docs/v1/tech/admin-guide/upgrade-new.adoc
 delete mode 100644 site/docs/v1/tech/admin-guide/upgrade-old.adoc

diff --git a/site/docs/v1/tech/admin-guide/upgrade-new.adoc b/site/docs/v1/tech/admin-guide/upgrade-new.adoc
deleted file mode 100644
index 8b55142da8..0000000000
--- a/site/docs/v1/tech/admin-guide/upgrade-new.adoc
+++ /dev/null
@@ -1,73 +0,0 @@
-First:
-
-reasons to upgrade
-reasons to not upgrade
-being aware of upgrade options, include release notifications
-Second, how to think about upgrades:
-
-Read the release notes. How do I tell if something affects me?
-How do I upgrade my custom theme (need to document how to do a diff of theme changes across versions, maybe even start a project that does that--pulls down the default theme from each released version of FusionAuth and commits it to a GH repo, perhaps part of this: https://github.com/FusionAuth/fusionauth-theme-helper )
-How do I migrate FusionAuth config changes between environments (pointing to/extracting content from this https://fusionauth.io/docs/v1/tech/admin-guide/configuration-management )
-
-How can I upgrade my database with minimal downtime?
-
-How do I switch out nodes if running in a cluster? What happens when the first node is switched out (it checks for the correct schema and upgrades if needed).
-
-How to handle main use cases: in dev envt, in docker/kubernetes, in cluster.
-
-Should I upgrade from 1.37 -> 1.43 jumping versions or step by step?
-
-How can customer know if upgrade will cause downtime? Can they use a staging envrionment to do so? If db migration is shown, yes, otherwise maybe? are there dev team todos to make this clearer? Can we talk about durations for a reference architecture. 
-
-Differentiate between an upgrade that has downtime around admin functionality and upgrade that affects end user login functionality (the old control plane/data plane metaphor)
-
-How to upgrade cloud instances (probably just excerpt the section in the cloud install guide)
-
-How do I know when a node is ready to serve traffic? Helm charts check /, some guidance around checking /api/status. Do we need a new endpoint?
-
-What is silent mode? It is make maintenance mode work, no prompts, non-silent mode means gui shows up asking for db connection info.
-
-
-Third, upgrade options:
-
-Easiest path
-
-take everything down, upgrade everything, start it back up,
-fusionatuh owns the schema, full outage
-Rolling upgrade
-
-If you have 3 nodes:
-
-Upgrade one node at a time behind an LB
-
-before adding upgraded node load balancer, node 1 upgrades
-or take node 2 and 3 at same time, so lose capacity, not schema mismatch
-Can stand up entirely new infra or run in-place upgrades using dpkg -i
-
-blue/green deployment
-
-Stand up 3 new nodes with new version on it. When adding node 4, it will lock db and own it. nodes 1, 2, 3 may error, may want to remove them. You can add node 4,5,6 at same time as you remove node 1,2,3, or wait for node 4 to complete upgrade. Again, this gets to informing the admin what the impact of an upgrade is.
-
-Out of band DB upgrades
-
-Another option do database updates out of band by yourself. If you have a three node cluster:
-
-stand up 3 new nodes with new version
-add maintenance page
-take all old version out of service
-run db updates using SQL
-connect three new nodes to the database (maybe need to bounce to get them to reconnect)
-add to load balancer.
-put in diagrams if possible
-
-faqs
-
-what is runtime mode and how does that affect upgrades
-what is maintenance mode
-what silent mode means
-how many versions can I skip
-
-we recommended migrating from one minor version to the next over
-how often should I upgrade
-whenever you want. it is your dependency and we won't force you. we recommend staying relatively close to the latest release. in addition, we don't typically backport bug fixes. so if you run into an issue, you'll need to upgrade to get the fix
-how can I find out about new releases
\ No newline at end of file
diff --git a/site/docs/v1/tech/admin-guide/upgrade-old.adoc b/site/docs/v1/tech/admin-guide/upgrade-old.adoc
deleted file mode 100644
index 2ba029f715..0000000000
--- a/site/docs/v1/tech/admin-guide/upgrade-old.adoc
+++ /dev/null
@@ -1,319 +0,0 @@
----
-layout: doc
-title: Upgrade FusionAuth
-description: Learn how to upgrade FusionAuth using our bundles and migration scripts
-navcategory: admin
----
-
-== Upgrading
-
-In order to upgrade FusionAuth to a later version use the following guides. Below you will find steps to follow if you are using `.deb` or `.rpm` package on Linux, or a `.zip` package on macOS, Linux or Windows.
-
-Topics covered in this document:
-
-* <<ZIP Packages>>
-* <<Linux Packages>>
-** <<Troubleshooting Upgrade with RPMs>>
-* <<FastPath>>
-* <<Database>>
-* <<Themes>>
-* <<Downtime>>
-
-If you used the FastPath or other installation methods initially, you may prefer to use that same mode to download the latest version of FusionAuth. If you would like to continue by manually downloading the necessary packages, read on.
-
-[NOTE]
-====
-*Readme*
-
-To upgrade to the latest version of FusionAuth using the FastPath installation go link:/docs/v1/tech/installation-guide/fast-path[here].
-
-To upgrade to the latest version of FusionAuth using Homebrew go link:/docs/v1/tech/installation-guide/homebrew[here].
-
-To upgrade to the latest version of FusionAuth using Docker go link:/docs/v1/tech/installation-guide/docker[here].
-
-If you want to use manual mode, download the latest version of FusionAuth and follow the instructions below. See https://fusionauth.io/download[Downloads].
-====
-
-
-== ZIP Packages
-
-FusionAuth is available in a zip package for macOS, Linux and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth.
-
-=== macOS and Linux
-
-In this example, we'll assume you have previously installed FusionAuth in `/usr/local/fusionauth` and this directory will be referred to `FUSIONAUTH_HOME`. If you have used a different directory you can adjust the following example accordingly.
-
-[source,title=Example filesystem layout]
-----
-/usr/local/fusionauth/bin
-/usr/local/fusionauth/config
-/usr/local/fusionauth/config/keystore
-/usr/local/fusionauth/config/fusionauth.properties
-/usr/local/fusionauth/data
-/usr/local/fusionauth/fusionauth-app
-/usr/local/fusionauth/fusionauth-search
-/usr/local/fusionauth/java
-----
-
-The first step will be to shutdown the FusionAuth services.
-
-[source,title=Shutdown and Uninstall FusionAuth]
-----
-# Stop Services
-/usr/local/fusionauth/bin/shutdown.sh
-
-# Delete or move existing installation
-cd /usr/local/fusionauth
-rm -rf ./fusionauth-app
-rm -rf ./fusionauth-search
-rm -rf ./bin
-----
-
-During an upgrade, most everything is saved in the database, so it is safe to delete these directories. To preserve your configuration and Elasticsearch index you want to be sure to preserve the following directories:
-
-[source,title=Preserve these directories]
-----
-/usr/local/fusionauth/config
-/usr/local/fusionauth/data
-/usr/local/fusionauth/java
-/usr/local/fusionauth/logs
-----
-
-Extract the new zips and place in `FUSIONAUTH_HOME`. In the following example, we are using the `unzip` command with the `-n` and the `-q` flags. The `-q` flag is optional, it causes the command to be run in quiet mode to reduce the amount of output to the console. The other flag `-n` is a no overwrite flag so that any configuration files are not overwritten.
-
-[source,title=Unzip the new packages with a no overwrite flag]
-----
-unzip -nq new-fusionauth-app.zip
-unzip -nq new-fusionauth-search.zip
-----
-
-Finally restart the FusionAuth services.
-
-[source,title=Startup FusionAuth]
-----
-# Start Services
-/usr/local/fusionauth/bin/startup.sh
-----
-
-=== Windows
-
-In this example, we'll assume you have previously installed FusionAuth in `\fusionauth` and this directory will be referred to `FUSIONAUTH_HOME`. If you have used a different directory you can adjust the following example accordingly.
-
-[source,title=Example filesystem layout]
-----
-\fusionauth\bin
-\fusionauth\config
-\fusionauth\config\keystore
-\fusionauth\config\fusionauth.properties
-\fusionauth\data
-\fusionauth\fusionauth-app
-\fusionauth\fusionauth-search
-\fusionauth\java
-----
-
-The first step will be to shutdown the FusionAuth services and delete the old installation.
-
-[source,title=Shutdown and Uninstall FusionAuth]
-----
-# Stop Services
-net stop FusionAuthApp
-net stop FusionAuthSearch
-
-# Uninstall Services
-cd \fusionauth\fusionauth-app\bin
-FusionAuthApp.exe /uninstall
-cd \fusionauth\fusionauth-search\elasticsearch\bin
-FusionAuthSearch.exe /uninstall
-
-# Delete or move existing installation
-cd \fusionauth
-move fusionauth-app fusionauth-app-old
-move fusionauth-search fusionauth-search-old
-----
-
-[NOTE]
-====
-Prior to version `1.37.0` the executable will be found in the `apache-tomcat` directory. For example,
-
-`\fusionauth\fusionauth-app\apache-tomcat\bin\FusionAuthApp.exe`
-
-Versions 1.37.0 through 1.39.0 do not support native Windows installation.
-====
-
-During an upgrade, most everything is saved in the database, so it is safe to delete these directories. To preserve your configuration and Elasticsearch index you want to be sure to preserve the following directories:
-
-[source,title=Preserve these directories]
-----
-\fusionauth\config
-\fusionauth\data
-\fusionauth\java
-\fusionauth\logs
-----
-
-Extract the new zips and place in `FUSIONAUTH_HOME`. You may do this using Windows File Explorer or other command line tools to unpack the zip archive. In this next step, ensure you delete or move the existing directories to ensure you do not unzip the new version on top of the existing version. If you do this, you will end up with duplicate libraries in the classpath that will lead to runtime errors.
-
-After you have extracted the new packages, re-install the Windows services and start them.
-
-[source,title=Install and Start FusionAuth]
-----
-# Install Windows Services
-cd \fusionauth\fusionauth-app\bin
-FusionAuthApp.exe /install
-cd \fusionauth\fusionauth-search\elasticsearch\bin
-FusionAuthSearch.exe /install
-
-# Startup Services
-net start FusionAuthSearch
-net start FusionAuthApp
-----
-
-[NOTE]
-====
-Prior to version 1.37.0 you can find `FusionAuthApp.exe` at
-
-`\fusionauth\fusionauth-app\apache-tomcat\bin\FusionAuthApp.exe`
-
-Versions 1.37.0 through 1.39.0 do not support native Windows installation.
-====
-
-That is it, you're done!
-
-== Linux Packages
-
-Updating your application is easy if you installed using the RPM or Debian packages. All you need to do is to issue an update command to the dpkg or rpm program and specify the new package file. Here is an example:
-
-[NOTE]
-====
-Running the update script will shut down the FusionAuth service if they have not yet been stopped The service will need to be restarted after the update is finished.
-====
-
-[source,title=Shutdown FusionAuth]
-----
-sudo service fusionauth-app stop
-sudo service fusionauth-search stop
-----
-
-[source,shell,title=Upgrade FusionAuth using Debian bundles]
-----
-sudo dpkg -i fusionauth-search-<version>.deb
-sudo dpkg -i fusionauth-app-<version>.deb
-----
-
-[source,shell,title=Upgrade FusionAuth using RPM bundles]
-----
-sudo rpm -U fusionauth-search-<version>.rpm
-sudo rpm -U fusionauth-app-<version>.rpm
-----
-
-[source,title=Start FusionAuth]
-----
-sudo systemctl start fusionauth-search
-sudo systemctl start fusionauth-app
-----
-
-=== Troubleshooting Upgrade with RPMs
-
-include::docs/v1/tech/shared/_troubleshooting-uninstall-upgrade-reinstall-rpm.adoc[]
-
-=== FastPath
-
-While FastPath is an option to perform an upgrade, the FastPath process limits the flexibility of installation in order to get up and running quickly. Therefore it is not recommended to use FastPath install scripts in a Production Environment.
-
-When in a production environment please utilize `.deb` or `.rpm` packages when on Linux. If you your production platform is macOS or Windows, please manually manage the upgrade using the `.zip` bundles.
-
-== Database
-
-[NOTE]
-====
-If you want FusionAuth to upgrade the database automatically, use the link:/docs/v1/tech/guides/silent-mode[Silent Mode] process, which will perform an automated upgrade.
-
-If you want to use Maintenance Mode, ensure your runtime mode is set to `development` and silent mode is set to `false`.
-
-If you want to upgrade the database manually, follow the instructions below.
-
-For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide] for reference.
-
-For more information on the various configuration options, see the link:/docs/v1/tech/reference/configuration[Configuration Reference].
-====
-
-[NOTE]
-====
-You should always backup your database prior to using Maintenance Mode.
-====
-
-Depending on your current version and the new version you will be updating to you might need to execute one or more SQL scripts to update your
- database. These scripts are located in the migrations folder inside the Database Schema ZIP file. This file can be downloaded by finding the database zip on the https://fusionauth.io/direct-download[Direct Downloads] page.
-
-[WARNING]
-====
-When upgrading your database from a previous version, be sure to only run the scripts located in the `migrations` folder, the base files
- `mysql.sql` and `postgresql.sql` should only be used during a clean installation when no database schema is present.
-====
-
-Inside of the database schema zip file, you will find the FusionAuth migrations. Run them in order, starting with the first migration greater than the version you are coming from, and ending with the version that is less than or equal to the target upgrade version.
-
-For example, if upgrading from version `1.19.1` to `1.22.0`, run the following SQL migrations in this order:
-
-* `1.20.0.sql`
-* `1.21.0.sql`
-* `1.22.0.sql`
-
-[source]
-----
-fusionauth-database-schema/
-|-- migrations/
-    |--  [mysql | postgresql]/
-      |-- 1.1.0.sql
-      |-- 1.2.0.sql
-      |-- 1.3.0.sql
-      |-- 1.3.1.sql
-      |-- 1.5.0.sql
-      |-- 1.6.0.sql
-      |-- 1.7.0.sql
-      |-- 1.7.1.sql
-      |-- 1.8.0-RC.1.sql
-      |-- 1.8.1-RC.1.sql
-      |-- 1.11.0.sql
-      |-- 1.12.0.sql
-      |-- 1.13.0.sql
-      |-- 1.14.0.sql
-      |-- 1.15.0.sql
-      |-- 1.15.3.sql
-      |-- 1.16.0-RC.1.sql
-      |-- 1.16.0.sql
-      |-- 1.17.0.sql
-      |-- 1.17.3.sql
-      |-- 1.18.0.sql
-      |-- 1.18.2.sql
-      |-- 1.19.0.sql
-      |-- 1.20.0.sql
-      |-- 1.21.0.sql
-      |-- 1.22.0.sql
-      |-- 1.23.0.sql
-      |-- 1.25.0.sql
-      |-- 1.26.0.sql
-      |-- 1.27.0.sql
-      |-- 1.28.0.sql
-      |-- 1.28.1.sql
-      |-- 1.29.1.sql
-      |-- 1.30.0.sql
-      |-- 1.30.1.sql
-      |-- 1.30.2.sql
-      |-- 1.32.0.sql
-      |-- 1.33.0.sql
-      |-- 1.35.0.sql
-      |-- 1.36.0.sql
-      |-- 1.37.0.sql
-      |-- 1.40.1.sql
-      |-- 1.41.0.sql
-      |-- 1.43.0.sql
-      |-- 1.44.0.sql
-----
-
-== Themes
-
-include::docs/v1/tech/installation-guide/_theme-upgrade.adoc[]
-
-== Downtime
-
-include::docs/v1/tech/installation-guide/_downtime-upgrade-limitation.adoc[]

From 3d1c6d0bf9ea6aaf3cf33a505f3a6044e7f9bebf Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <gareth@ritza.co>
Date: Wed, 10 May 2023 13:38:31 +0200
Subject: [PATCH 10/55] fix header, note, image

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 265d40a0d5..594d938a12 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -15,7 +15,7 @@ Topics covered in this document:
 ** <<Reasons to Upgrade>>
 ** <<Reasons Not to Upgrade>>
 ** <<Being Aware of Upgrade Options>>
-* <<Thinking About Upgrades>>
+* <<How to Think About Upgrades>>
 ** <<Update Contents and Notes>>
 ** <<Testing>>
 ** <<Downtime and Database Migrations>>
@@ -86,7 +86,7 @@ If you want to interactively (called link:/docs/v1/tech/installation-guide/fusio
 [NOTE]
 ====
 You should always backup your database prior to using Maintenance Mode, or performing any database migrations by any method.
-====.
+====
 
 The timing of the database upgrade is also important to note. When an upgraded node is added to a FusionAuth cluster, it will lock the database and perform the database upgrade if configured for Silent Mode. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. 
 
@@ -142,7 +142,7 @@ A procedure might look like this:
 
 This way there is still some downtime, but it is limited to the time it takes to run the database migration on the upgraded first node. There will be limited capacity during the upgrade, especially while the second and third nodes are upgrading, but the system will be available for use for the majority of the upgrade process.
 
-{% include _image.liquid src="/assets/img/docs/admin-guide/upgrade/blue-green.svg " alt="A representation of a Rolling upgrade." class="img-fluid" figure=true %}
+image::admin-guide/upgrade/blue-green.svg[A representation of a Rolling upgrade.,width=600]
 
 === Blue/Green Deployment
 
@@ -150,7 +150,7 @@ A blue / green deployment is a technique that reduces downtime and risk by runni
 
 To perform a blue/green deployment with a 3 node cluster, first create 3 entirely new nodes. Add one of these nodes to the existing cluster. At this point, the new node will lock the database, and own it while it completes the database upgrade. The original nodes might start to error, as they will not have access to the database. They can be removed. The remaining new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
 
-{% include _image.liquid src="/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg" alt="A representation of a Blue/Green upgrade." class="img-fluid" figure=true %}
+image::admin-guide/upgrade/rolling-upgrade.svg[A representation of a Blue/Green upgrade.,width=600]
  
 === Out of Band Database Upgrades
 

From 6719f533ad35d8f6397340476666d099d058cde2 Mon Sep 17 00:00:00 2001
From: worktheclock <85885287+worktheclock@users.noreply.github.com>
Date: Thu, 11 May 2023 18:16:29 +0200
Subject: [PATCH 11/55] Upgrading language edit

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 186 ++++++++++-----------
 1 file changed, 93 insertions(+), 93 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 594d938a12..66708747b0 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -7,13 +7,13 @@ navcategory: admin
 
 == Upgrading
 
-In order to upgrade FusionAuth to a later version, there are a number of things to consider. This document will help you understand the upgrade process, and how to plan for it. It also covers detailed instructions on how to upgrade FusionAuth on various platforms and distributions.
+If you're considering upgrading FusionAuth to a later version, this document will help you understand the upgrade process and how to plan for it. It also covers detailed instructions on how to upgrade FusionAuth on various platforms and distributions.
 
 Topics covered in this document:
 
 * <<When to Upgrade>>
 ** <<Reasons to Upgrade>>
-** <<Reasons Not to Upgrade>>
+** <<Reasons not to Upgrade>>
 ** <<Being Aware of Upgrade Options>>
 * <<How to Think About Upgrades>>
 ** <<Update Contents and Notes>>
@@ -21,13 +21,13 @@ Topics covered in this document:
 ** <<Downtime and Database Migrations>>
 ** <<Connected Applications and Client Libraries>>
 ** <<Skipping Versions>>
-** <<Migrating Configuration between Environments>>
+** <<Migrating Configuration Between Environments>>
 ** <<Themes and Customizations>>
 * <<Upgrade Options>>
 ** <<Easiest Route>>
 ** <<Rolling Upgrade>>
-** <<Blue/Green Deployment>>
-** <<Out of Band Database Upgrades>>
+** <<Blue-Green Deployment>>
+** <<Out-of-Band Database Upgrades>>
 * <<FAQs>>
 * <<Detailed Upgrade Instructions>>
 * <<ZIP Packages>>
@@ -42,26 +42,26 @@ Topics covered in this document:
 
 Upgrading to a newer version of FusionAuth can provide the following benefits:
 
-. Access to new features and improvements
-. Improved performance and stability
-. Critical Security updates and patches
+* Access to new features and improvements.
+* Improved performance and stability.
+* Critical Security updates and patches.
 
-=== Reasons Not to Upgrade
+=== Reasons not to Upgrade
 
 You might want to delay upgrading in the following situations:
 
-. Your current version is meeting all your requirements
-. You are in the middle of a project or have tight deadlines
-. You have concerns about compatibility with customizations or third-party integrations
+* Your current version meets all your requirements.
+* You are in the middle of a project or have tight deadlines.
+* You have concerns about compatibility with customizations or third-party integrations.
 
 === Being Aware of Upgrade Options
 
 You can stay informed about new FusionAuth releases and updates by:
 
-. Monitoring the link:/docs/v1/tech/release-notes[release notes]
-. Join the https://fusionauth.io/community[FusionAuth Community site] and https://fusionauth.slack.com/join/shared_invite/zt-6ykfov9u-MTwA1A6ptv0Gr6KcFBVG4w#/shared-invite/email[Slack channel]
-. Following FusionAuth on social media platforms, including https://twitter.com/FusionAuth[Twitter] and https://www.linkedin.com/company/fusionauth[LinkedIn].
-. Monitoring the https://github.com/FusionAuth/[FusionAuth GitHub repository]
+* Monitoring the link:/docs/v1/tech/release-notes[release notes].
+* Joining the https://fusionauth.io/community[FusionAuth Community site] and https://fusionauth.slack.com/join/shared_invite/zt-6ykfov9u-MTwA1A6ptv0Gr6KcFBVG4w#/shared-invite/email[Slack channel].
+* Following FusionAuth on social media platforms, including https://twitter.com/FusionAuth[Twitter] and https://www.linkedin.com/company/fusionauth[LinkedIn].
+* Monitoring the https://github.com/FusionAuth/[FusionAuth GitHub repository].
 
 == How to Think About Upgrades
 
@@ -69,45 +69,45 @@ Before upgrading FusionAuth, there are a number of things to consider. Go throug
 
 === Update Contents and Notes
 
-Read the link:/docs/v1/tech/release-notes[release notes].  Release notes help you understand if an update affects you. They include details on new features, improvements, bug fixes, and potential breaking changes.
+Read the link:/docs/v1/tech/release-notes[release notes]. Release notes help you understand how an update affects you. They include details on new features, improvements, bug fixes, and potential breaking changes.
 
 === Testing
 
-Before starting the upgrade process on production, test the upgrade in a staging or development environment to identify potential issues. This is particularly important on more complex upgrades involving multiple version jumps, or if you have made customizations to FusionAuth.
+Before starting the upgrade process on production, test the upgrade in a staging or development environment to identify potential issues. This is particularly important on more complex upgrades involving multiple version jumps or if you have made customizations to FusionAuth.
 
 === Downtime and Database Migrations
 
-Plan for any downtime or maintenance windows required for the upgrade. If changes to the database schema are required, this could require more steps and downtime that affects end users. A pure application upgrade on the other hand may only affect admin functionality, and not require any downtime from an end user perspective.
+Plan for any downtime or maintenance windows required for the upgrade. If changes to the database schema are required, this could require more steps and downtime that affects end users. A pure application upgrade, on the other hand, may only affect admin functionality and not require any downtime from an end-user perspective.
 
-FusionAuth can perform database migrations automatically and silently using called link:/docs/v1/tech/guides/silent-mode[Silent Mode]. 
+FusionAuth can perform database migrations automatically and silently using a process called link:/docs/v1/tech/guides/silent-mode[Silent Mode]. 
 
-If you want to interactively (called link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode]), or you can run any needed scripts out of band (meaning directly on the database yourself). 
+If you want to run the migrations interactively, use link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode], or you can run any needed scripts out of band (meaning directly on the database yourself).
 
 [NOTE]
 ====
-You should always backup your database prior to using Maintenance Mode, or performing any database migrations by any method.
+You should always back up your database before using Maintenance Mode or performing any database migrations by any method.
 ====
 
 The timing of the database upgrade is also important to note. When an upgraded node is added to a FusionAuth cluster, it will lock the database and perform the database upgrade if configured for Silent Mode. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. 
 
 === Connected Applications and Client Libraries
 
-Consider that a FusionAuth server upgrade might mean that you need to upgrade your client libraries as well. Check before upgrading if this is needed, as it will entail a more complex upgrade process, and may require more downtime.
+Consider that a FusionAuth server upgrade might mean that you need to upgrade your client libraries too. Check if this is needed before upgrading, as it will entail a more complex upgrade process and may require more downtime.
 
 === Skipping Versions 
 
-Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. This is called a "version jump". FusionAuth migration can run all the necessary database migrations to get you to the latest version. However, we recommend that you don't skip minor versions, and rather migrate from one minor version to the next, step by step. For example, if you want to get to version 1.43, and you are on version 1.37, we recommend that you upgrade to each minor step to 1.43.
+Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. This is called a "version jump". FusionAuth migration can run all the necessary database migrations to get you to the latest version. However, we recommend that you don't skip minor versions and rather migrate from one minor version to the next, step by step. For example, if you are on version 1.37 and want to get to version 1.43, we recommend that you upgrade each minor step to 1.43.
 
-=== Migrating Configuration between Environments
+=== Migrating Configuration Between Environments
 
-There are a number of options you can use to manage the configuration of your FusionAuth instance over time, as well as to promote changes from one environment. These include:
+There are a number of options for managing the configuration of your FusionAuth instance over time and promoting changes from one environment to another. These include:
 
-- Script The Changes
+- Script the changes
 - Terraform
 - Pulumi
-- Manual Configuration via the UI
+- Manual configuration via the UI
 
-You can read more at link:/docs/v1/tech/admin-guide/configuration-management[the Configuration Management guide].
+You can read more in link:/docs/v1/tech/admin-guide/configuration-management[the Configuration Management guide].
 
 === Themes and Customizations
 
@@ -121,50 +121,50 @@ include::docs/v1/tech/installation-guide/_theme-upgrade.adoc[]
 
 The easiest upgrade route is to simply stop all your services, upgrade everything, and then bring it all back online. 
 
-This is a good option for single instance development or QA systems, or for systems that can tolerate longer amounts of downtime.
+This is a good option for single-instance development or QA systems, or for systems that can tolerate longer periods of downtime.
 
-If minimizing downtime is a goal, then rolling upgrades, or a blue/green deployment might be more suitable. 
+If minimizing downtime is a goal, then rolling upgrades or a blue-green deployment might be more suitable. 
 
 === Rolling Upgrade
 
-You can perform a rolling upgrade if you have 3 FusionAuth nodes running behind a load balancer. Each node is upgraded one at a time, and the load balancer is configured to direct traffic to the upgraded nodes as they become available for use. This allows you to upgrade FusionAuth with minimal downtime. 
+You can perform a rolling upgrade if you have three FusionAuth nodes running behind a load balancer. The nodes are upgraded one at a time and the load balancer is configured to direct traffic to the upgraded nodes as they become available for use. This allows you to upgrade FusionAuth with minimal downtime. 
 
 Because individual nodes are taken offline during the rolling update, the capacity of your installation is reduced during the upgrade.
 
-You can choose to run in-place upgrades on each node, or to replace each node with a new node running the latest version of FusionAuth. In place upgrades are potentially faster, but if something goes wrong, you may need to roll back the upgrade. Replacing nodes may be slower, but if something goes wrong, you can simply revert to the previous version of FusionAuth by pointing the load balancer to the old nodes.
+You can choose to run in-place upgrades on each node or to replace each node with a new node running the latest version of FusionAuth. In-place upgrades are potentially faster, but if something goes wrong, you may need to roll back the upgrade. Replacing nodes may be slower, but if something goes wrong, you can simply revert to the previous version of FusionAuth by pointing the load balancer to the old nodes.
 
-A procedure might look like this:
-- Stop the first node, and remove it from the load balancer
-- Upgrade FusionAuth on first node. After FusionAuth is update, you can start it up, so that it can perform the database migrations. This will lock the database, and own it while it completes the database upgrade. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may error while the first node is being upgraded.
-- Start the first node, and add it back to the load balancer
-- Stop the second and third nodes, and remove them from the load balancer, and upgrade them. 
-- Start the second and third nodes, and add them back to the load balancer
+A rolling upgrade procedure might look like this:
+- Stop the first node and remove it from the load balancer.
+- Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded.
+- Start the first node and add it back to the load balancer.
+- Stop the second and third nodes, remove them from the load balancer, and upgrade them. 
+- Start the second and third nodes and add them back to the load balancer.
 
-This way there is still some downtime, but it is limited to the time it takes to run the database migration on the upgraded first node. There will be limited capacity during the upgrade, especially while the second and third nodes are upgrading, but the system will be available for use for the majority of the upgrade process.
+There is still some downtime with this procedure, but it is limited to the time it takes to run the database migration on the upgraded first node. There will be limited capacity during the upgrade, especially while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
 
 image::admin-guide/upgrade/blue-green.svg[A representation of a Rolling upgrade.,width=600]
 
-=== Blue/Green Deployment
+=== Blue-Green Deployment
 
-A blue / green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue / green deployment instead of performing a rolling upgrade completely isolates the upgrade process from the production environment, reducing impact and risk to the current production environment.
+A blue-green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue-green deployment instead of performing a rolling upgrade isolates the upgrade process from the production environment, reducing the impact and risk to the current production environment.
 
-To perform a blue/green deployment with a 3 node cluster, first create 3 entirely new nodes. Add one of these nodes to the existing cluster. At this point, the new node will lock the database, and own it while it completes the database upgrade. The original nodes might start to error, as they will not have access to the database. They can be removed. The remaining new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
+To perform a blue-green deployment with a three-node cluster, first create three new nodes. Add one of these nodes to the existing cluster. At this point, the new node will lock the database and own it while it completes the database upgrade. The original nodes might give errors, as they will not have access to the database. They can be removed. The remaining new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
 
 image::admin-guide/upgrade/rolling-upgrade.svg[A representation of a Blue/Green upgrade.,width=600]
  
-=== Out of Band Database Upgrades
+=== Out-of-Band Database Upgrades
 
-While FusionAuth can handle database migrations completely automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode] or interactively using Maintenance Mode, you may want to perform the database upgrade yourself. This is useful if you want to perform the database upgrade in a way that minimizes downtime, or as part of a larger automated or coordinated deployment. The scripts for the database migrations are available in the FusionAuth upgrade packages. 
+While FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode] or interactively using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode], you may want to perform the database upgrade yourself. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. The scripts for the database migrations are available in the FusionAuth upgrade packages. 
 
-Depending on your current version and the new version you will be updating to you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder inside the Database Schema ZIP file. This file can be downloaded by finding the database zip on the https://fusionauth.io/direct-download[Direct Downloads] page.
+Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the https://fusionauth.io/direct-download[Direct Downloads] page.
 
 [WARNING]
 ====
-When upgrading your database from a previous version, be sure to only run the scripts located in the `migrations` folder, the base files
+When upgrading your database from a previous version, be sure to only run the scripts located in the `migrations` folder. The base files
  `mysql.sql` and `postgresql.sql` should only be used during a clean installation when no database schema is present.
 ====
 
-Inside of the database schema zip file, you will find the FusionAuth migrations. Run them in order, starting with the first migration greater than the version you are coming from, and ending with the version that is less than or equal to the target upgrade version.
+Find the FusionAuth migrations in the Database Schema ZIP file. Run them in order, starting with the first migration greater than the version you are coming from, and ending with the version that is less than or equal to the target upgrade version.
 
 For example, if upgrading from version `1.19.1` to `1.22.0`, run the following SQL migrations in this order:
 
@@ -227,22 +227,22 @@ fusionauth-database-schema/
 
 == FAQs
 
-Q: What is runtime mode and how does that affect upgrades?
-A: FusionAuth's Runtime mode can either be 'production' or "development". When in the `development`` runtime mode, maintenance mode will interactively assist you configuring the database and connecting to Elasticsearch if configured. Once you move FusionAuth into production, it is recommended that you modify the runtime mode to `production`. When in production runtime mode maintenance mode will no longer be available to you which means you can be certain that your end users will not find themselves on the database upgrade panel during an Upgrade. When in production mode you will either need to leverage Silent Mode to automatically apply database migrations or you will need to apply the database migrations yourself (either by hand or via a script of some sort).For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide] for reference.
+Q: What is runtime mode and how does it affect upgrades? +  
+A: FusionAuth runtime mode can be either `production` or `development`. When in the `development` runtime mode, Maintenance Mode will interactively assist you to configure the database and connect to Elasticsearch, if configured. Once you move FusionAuth into production, it is recommended that you modify the runtime mode to `production`. When in `production` runtime mode, Maintenance Mode will no longer be available to you, which means you can be certain that your end users will not find themselves on the database upgrade panel during an upgrade. When in `production` mode, you will either need to leverage Silent Mode to automatically apply database migrations or you will need to apply the database migrations yourself (either by hand or via a script of some sort). For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide].
 
-Q: What is Maintenance Mode?
-A: Maintenance Mode is a special admin interface for FusionAuth, which is helpful to interactively upgrade FusionAuth or setup database connections. You can switch to Maintenance mode by switching to the `development` runtime mode, and setting Silent Mode to false. 
+Q: What is Maintenance Mode? +
+A: Maintenance Mode is a special admin interface for FusionAuth that helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. 
 
-Q: What is Silent Mode?
-A: link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments, or for when you want to upgrade FusionAuth without using the Maintenance Mode interface. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in `production` runtime mode as well. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will switch to the manual Maintenance Mode interface.
+Q: What is Silent Mode? +
+A: link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments or for when you want to upgrade FusionAuth without using the Maintenance Mode interface. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in `production` runtime mode too. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will switch to the manual Maintenance Mode interface.
 
-Q: How many versions can I skip?
-A: We recommended migrating from one minor version to the next over. 
+Q: How many versions can I skip? +
+A: We recommended migrating from one minor version to the next. 
 
-Q: How often should I upgrade?
-A: You can upgrade whenever you want. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release. In addition, we don't typically backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix.
+Q: How often should I upgrade? +
+A: You can upgrade whenever you want to. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release. In addition, we don't typically backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix.
 
-Q: How can I find out about new releases?
+Q: How can I find out about new releases? +
 A: We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. 
 
 
@@ -254,11 +254,11 @@ This section will guide you with detailed technical instructions on how to upgra
 ====
 *Readme*
 
-To upgrade to the latest version of FusionAuth using the FastPath installation go link:/docs/v1/tech/installation-guide/fast-path[here].
+To upgrade to the latest version of FusionAuth using the FastPath installation, go link:/docs/v1/tech/installation-guide/fast-path[here].
 
-To upgrade to the latest version of FusionAuth using Homebrew go link:/docs/v1/tech/installation-guide/homebrew[here].
+To upgrade to the latest version of FusionAuth using Homebrew, go link:/docs/v1/tech/installation-guide/homebrew[here].
 
-To upgrade to the latest version of FusionAuth using Docker go link:/docs/v1/tech/installation-guide/docker[here].
+To upgrade to the latest version of FusionAuth using Docker, go link:/docs/v1/tech/installation-guide/docker[here].
 
 If you want to use manual mode, download the latest version of FusionAuth and follow the instructions below. See https://fusionauth.io/download[Downloads].
 ====
@@ -266,11 +266,11 @@ If you want to use manual mode, download the latest version of FusionAuth and fo
 
 === ZIP Packages
 
-FusionAuth is available in a zip package for macOS, Linux and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth.
+FusionAuth is available in a ZIP package for macOS, Linux, and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth.
 
 ==== macOS and Linux
 
-In this example, we'll assume you have previously installed FusionAuth in `/usr/local/fusionauth` and this directory will be referred to `FUSIONAUTH_HOME`. If you have used a different directory you can adjust the following example accordingly.
+In this example, we'll assume you have previously installed FusionAuth in `/usr/local/fusionauth` and this directory will be referred to as `FUSIONAUTH_HOME`. If you have used a different directory you can adjust the following example accordingly.
 
 [source,title=Example filesystem layout]
 ----
@@ -284,11 +284,11 @@ In this example, we'll assume you have previously installed FusionAuth in `/usr/
 /usr/local/fusionauth/java
 ----
 
-The first step will be to shutdown the FusionAuth services.
+The first step will be to shut down the FusionAuth services.
 
-[source,title=Shutdown and Uninstall FusionAuth]
+[source,title=Shut down and uninstall FusionAuth]
 ----
-# Stop Services
+# Stop services
 /usr/local/fusionauth/bin/shutdown.sh
 
 # Delete or move existing installation
@@ -298,7 +298,7 @@ rm -rf ./fusionauth-search
 rm -rf ./bin
 ----
 
-During an upgrade, most everything is saved in the database, so it is safe to delete these directories. To preserve your configuration and Elasticsearch index you want to be sure to preserve the following directories:
+During an upgrade, most everything is saved in the database, so it is safe to delete these directories. To preserve your configuration and Elasticsearch index, you want to be sure to preserve the following directories:
 
 [source,title=Preserve these directories]
 ----
@@ -308,17 +308,17 @@ During an upgrade, most everything is saved in the database, so it is safe to de
 /usr/local/fusionauth/logs
 ----
 
-Extract the new zips and place in `FUSIONAUTH_HOME`. In the following example, we are using the `unzip` command with the `-n` and the `-q` flags. The `-q` flag is optional, it causes the command to be run in quiet mode to reduce the amount of output to the console. The other flag `-n` is a no overwrite flag so that any configuration files are not overwritten.
+Extract the new ZIP files and place them in `FUSIONAUTH_HOME`. In the following example, we use the `unzip` command with the `-n` and `-q` flags. The `-q` flag is optional, it causes the command to be run in quiet mode to reduce the amount of output to the console. The other flag `-n` is a no-overwrite flag so that any configuration files are not overwritten.
 
-[source,title=Unzip the new packages with a no overwrite flag]
+[source,title=Unzip the new packages with a no-overwrite flag]
 ----
 unzip -nq new-fusionauth-app.zip
 unzip -nq new-fusionauth-search.zip
 ----
 
-Finally restart the FusionAuth services.
+Finally, restart the FusionAuth services.
 
-[source,title=Startup FusionAuth]
+[source,title=Start up FusionAuth]
 ----
 # Start Services
 /usr/local/fusionauth/bin/startup.sh
@@ -326,7 +326,7 @@ Finally restart the FusionAuth services.
 
 ==== Windows
 
-In this example, we'll assume you have previously installed FusionAuth in `\fusionauth` and this directory will be referred to `FUSIONAUTH_HOME`. If you have used a different directory you can adjust the following example accordingly.
+In this example, we'll assume you have previously installed FusionAuth in `\fusionauth` and this directory will be referred to as `FUSIONAUTH_HOME`. If you have used a different directory, you can adjust the following example accordingly.
 
 [source,title=Example filesystem layout]
 ----
@@ -340,9 +340,9 @@ In this example, we'll assume you have previously installed FusionAuth in `\fusi
 \fusionauth\java
 ----
 
-The first step will be to shutdown the FusionAuth services and delete the old installation.
+The first step will be to shut down the FusionAuth services and delete the old installation.
 
-[source,title=Shutdown and Uninstall FusionAuth]
+[source,title=Shut down and uninstall FusionAuth]
 ----
 # Stop Services
 net stop FusionAuthApp
@@ -362,14 +362,14 @@ move fusionauth-search fusionauth-search-old
 
 [NOTE]
 ====
-Prior to version `1.37.0` the executable will be found in the `apache-tomcat` directory. For example,
+Prior to version 1.37.0, the executable will be found in the `apache-tomcat` directory. For example,
 
 `\fusionauth\fusionauth-app\apache-tomcat\bin\FusionAuthApp.exe`
 
 Versions 1.37.0 through 1.39.0 do not support native Windows installation.
 ====
 
-During an upgrade, most everything is saved in the database, so it is safe to delete these directories. To preserve your configuration and Elasticsearch index you want to be sure to preserve the following directories:
+During an upgrade, most everything is saved in the database, so it is safe to delete these directories. To preserve your configuration and Elasticsearch index, you want to be sure to preserve the following directories:
 
 [source,title=Preserve these directories]
 ----
@@ -379,11 +379,11 @@ During an upgrade, most everything is saved in the database, so it is safe to de
 \fusionauth\logs
 ----
 
-Extract the new zips and place in `FUSIONAUTH_HOME`. You may do this using Windows File Explorer or other command line tools to unpack the zip archive. In this next step, ensure you delete or move the existing directories to ensure you do not unzip the new version on top of the existing version. If you do this, you will end up with duplicate libraries in the classpath that will lead to runtime errors.
+Extract the new ZIP files and place them in `FUSIONAUTH_HOME`. You may do this using Windows File Explorer or other command line tools to unpack the ZIP archive. In this next step, ensure you delete or move the existing directories to prevent unzipping the new version on top of the existing version. If the new version is unzipped on top of the existing version, you will end up with duplicate libraries in the classpath that will lead to runtime errors.
 
-After you have extracted the new packages, re-install the Windows services and start them.
+After you have extracted the new packages, reinstall the Windows services and start them.
 
-[source,title=Install and Start FusionAuth]
+[source,title=Install and start FusionAuth]
 ----
 # Install Windows Services
 cd \fusionauth\fusionauth-app\bin
@@ -398,25 +398,25 @@ net start FusionAuthApp
 
 [NOTE]
 ====
-Prior to version 1.37.0 you can find `FusionAuthApp.exe` at
+Prior to version 1.37.0 you can find `FusionAuthApp.exe` at:
 
 `\fusionauth\fusionauth-app\apache-tomcat\bin\FusionAuthApp.exe`
 
 Versions 1.37.0 through 1.39.0 do not support native Windows installation.
 ====
 
-That is it, you're done!
+
 
 === Linux Packages
 
-Updating your application is easy if you installed using the RPM or Debian packages. All you need to do is to issue an update command to the dpkg or rpm program and specify the new package file. Here is an example:
+Updating your application is easy if you installed using the RPM or Debian packages. All you need to do is to issue an update command to the `dpkg` or RPM program and specify the new package file. Here is an example:
 
 [NOTE]
 ====
-Running the update script will shut down the FusionAuth service if they have not yet been stopped The service will need to be restarted after the update is finished.
+Running the update script will shut down the FusionAuth service if it has not yet been stopped. The service will need to be restarted after the update is finished.
 ====
 
-[source,title=Shutdown FusionAuth]
+[source,title=Shut down FusionAuth]
 ----
 sudo service fusionauth-app stop
 sudo service fusionauth-search stop
@@ -446,9 +446,9 @@ include::docs/v1/tech/shared/_troubleshooting-uninstall-upgrade-reinstall-rpm.ad
 
 === FastPath
 
-While FastPath is an option to perform an upgrade, the FastPath process limits the flexibility of installation in order to get up and running quickly. Therefore it is not recommended to use FastPath install scripts in a Production Environment.
+While FastPath is an option to perform an upgrade, the FastPath process limits the flexibility of the installation in order to get it up and running quickly. We therefore don't recommend you use FastPath install scripts in a production environment.
 
-When in a production environment please utilize `.deb` or `.rpm` packages when on Linux. If you your production platform is macOS or Windows, please manually manage the upgrade using the `.zip` bundles.
+On Linux in a production environment, use `.deb` or `.rpm` packages. If your production platform is macOS or Windows, please manually manage the upgrade using the `.zip` bundles.
 
 === Database
 
@@ -456,29 +456,29 @@ When in a production environment please utilize `.deb` or `.rpm` packages when o
 ====
 If you want FusionAuth to upgrade the database automatically, use the link:/docs/v1/tech/guides/silent-mode[Silent Mode] process, which will perform an automated upgrade.
 
-If you want to use Maintenance Mode, ensure your runtime mode is set to `development` and silent mode is set to `false`.
+If you want to use Maintenance Mode, ensure your runtime mode is set to `development` and Silent Mode is set to `false`.
 
 If you want to upgrade the database manually, follow the instructions below.
 
-For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide] for reference.
+For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide].
 
 For more information on the various configuration options, see the link:/docs/v1/tech/reference/configuration[Configuration Reference].
 ====
 
 [NOTE]
 ====
-You should always backup your database prior to upgrading using Maintenance Mode.
+You should always back up your database before upgrading using Maintenance Mode.
 ====
 
-Depending on your current version and the new version you will be updating to you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder inside the Database Schema ZIP file. This file can be downloaded by finding the database zip on the https://fusionauth.io/direct-download[Direct Downloads] page.
+Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the https://fusionauth.io/direct-download[Direct Downloads] page.
 
 [WARNING]
 ====
-When upgrading your database from a previous version, be sure to only run the scripts located in the `migrations` folder, the base files
+When upgrading your database from a previous version, be sure to only run the scripts located in the `migrations` folder. The base files
  `mysql.sql` and `postgresql.sql` should only be used during a clean installation when no database schema is present.
 ====
 
-Inside of the database schema zip file, you will find the FusionAuth migrations. Run them in order, starting with the first migration greater than the version you are coming from, and ending with the version that is less than or equal to the target upgrade version.
+Find the FusionAuth migrations in the Database Schema ZIP file. Run them in order, starting with the first migration greater than the version you are coming from, and ending with the version that is less than or equal to the target upgrade version.
 
 For example, if upgrading from version `1.19.1` to `1.22.0`, run the following SQL migrations in this order:
 

From 9a6783364cfef0e43313146272b5b10ac9639b5c Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:16:04 +0200
Subject: [PATCH 12/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 66708747b0..cc1c2bf039 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -44,7 +44,7 @@ Upgrading to a newer version of FusionAuth can provide the following benefits:
 
 * Access to new features and improvements.
 * Improved performance and stability.
-* Critical Security updates and patches.
+* Critical security updates and patches.
 
 === Reasons not to Upgrade
 

From a0a35e7ef14f71f6c3825c01e8f1a84f09c9c3eb Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:16:10 +0200
Subject: [PATCH 13/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index cc1c2bf039..42a0d2973c 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -46,7 +46,7 @@ Upgrading to a newer version of FusionAuth can provide the following benefits:
 * Improved performance and stability.
 * Critical security updates and patches.
 
-=== Reasons not to Upgrade
+=== Reasons Not To Upgrade
 
 You might want to delay upgrading in the following situations:
 

From a776910abf2ffafdb9d5edb51eac2e7c20caa713 Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:16:18 +0200
Subject: [PATCH 14/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 42a0d2973c..7db241b78b 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -38,7 +38,7 @@ Topics covered in this document:
 
 == When to Upgrade
 
-=== Reasons to Upgrade
+=== Reasons To Upgrade
 
 Upgrading to a newer version of FusionAuth can provide the following benefits:
 

From 6a4b877a89a283773ed4921de8ce42e26dd7f57d Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:16:25 +0200
Subject: [PATCH 15/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 7db241b78b..c2a9463b39 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -59,7 +59,7 @@ You might want to delay upgrading in the following situations:
 You can stay informed about new FusionAuth releases and updates by:
 
 * Monitoring the link:/docs/v1/tech/release-notes[release notes].
-* Joining the https://fusionauth.io/community[FusionAuth Community site] and https://fusionauth.slack.com/join/shared_invite/zt-6ykfov9u-MTwA1A6ptv0Gr6KcFBVG4w#/shared-invite/email[Slack channel].
+* Joining the https://fusionauth.io/community[FusionAuth community] forum and/or slack.
 * Following FusionAuth on social media platforms, including https://twitter.com/FusionAuth[Twitter] and https://www.linkedin.com/company/fusionauth[LinkedIn].
 * Monitoring the https://github.com/FusionAuth/[FusionAuth GitHub repository].
 

From 8020b05cd15fc1d9cb1cfce07bf1c0ddeb2220ef Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:16:36 +0200
Subject: [PATCH 16/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index c2a9463b39..fd7be3c427 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -61,7 +61,7 @@ You can stay informed about new FusionAuth releases and updates by:
 * Monitoring the link:/docs/v1/tech/release-notes[release notes].
 * Joining the https://fusionauth.io/community[FusionAuth community] forum and/or slack.
 * Following FusionAuth on social media platforms, including https://twitter.com/FusionAuth[Twitter] and https://www.linkedin.com/company/fusionauth[LinkedIn].
-* Monitoring the https://github.com/FusionAuth/[FusionAuth GitHub repository].
+* Monitoring the https://github.com/FusionAuth/fusionauth-issues/issues[FusionAuth Issues GitHub repository].
 
 == How to Think About Upgrades
 

From 62db04c4c3d8812f05eff1845f6bced24ab93073 Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:16:46 +0200
Subject: [PATCH 17/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index fd7be3c427..26d5e9c83d 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -65,7 +65,7 @@ You can stay informed about new FusionAuth releases and updates by:
 
 == How to Think About Upgrades
 
-Before upgrading FusionAuth, there are a number of things to consider. Go through each of the points below to see if any of them apply to your situation.
+Before upgrading FusionAuth, there are a number of things to consider. Upgrading FusionAuth is similar to upgrading a library your application depends on. Go through each of the points below to see if any of them apply to your situation.
 
 === Update Contents and Notes
 

From 48ee59a7ac55561afd6bdb98708e9c0c719530c0 Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:16:56 +0200
Subject: [PATCH 18/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 26d5e9c83d..29eeda7e98 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -77,7 +77,7 @@ Before starting the upgrade process on production, test the upgrade in a staging
 
 === Downtime and Database Migrations
 
-Plan for any downtime or maintenance windows required for the upgrade. If changes to the database schema are required, this could require more steps and downtime that affects end users. A pure application upgrade, on the other hand, may only affect admin functionality and not require any downtime from an end-user perspective.
+Plan for any downtime or maintenance windows required for the upgrade. If changes to the database schema are required, this could require more steps and downtime that affects end users. Such changes are always noted in the release notes. (Read the release notes carefully.) A pure application upgrade, on the other hand, may not require any downtime from an end-user perspective.
 
 FusionAuth can perform database migrations automatically and silently using a process called link:/docs/v1/tech/guides/silent-mode[Silent Mode]. 
 

From b63000a1bab35d944836e2b593880a09bd7522ac Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:17:07 +0200
Subject: [PATCH 19/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 29eeda7e98..0f62022657 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -88,7 +88,7 @@ If you want to run the migrations interactively, use link:/docs/v1/tech/installa
 You should always back up your database before using Maintenance Mode or performing any database migrations by any method.
 ====
 
-The timing of the database upgrade is also important to note. When an upgraded node is added to a FusionAuth cluster, it will lock the database and perform the database upgrade if configured for Silent Mode. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. 
+The timing of the database upgrade is also important to note. When an upgraded node is added to a FusionAuth cluster, it will lock the database and perform the database upgrade if configured for Silent Mode and the database requires upgrading. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. 
 
 === Connected Applications and Client Libraries
 

From 980b979a9bad0e810003dc9667ddc2508be473f6 Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:17:24 +0200
Subject: [PATCH 20/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 0f62022657..b798d30155 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -94,6 +94,8 @@ The timing of the database upgrade is also important to note. When an upgraded n
 
 Consider that a FusionAuth server upgrade might mean that you need to upgrade your client libraries too. Check if this is needed before upgrading, as it will entail a more complex upgrade process and may require more downtime.
 
+In general, client libraries are forward compatible, but any issues will be noted in the release notes. (Read the release notes carefully.)
+
 === Skipping Versions 
 
 Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. This is called a "version jump". FusionAuth migration can run all the necessary database migrations to get you to the latest version. However, we recommend that you don't skip minor versions and rather migrate from one minor version to the next, step by step. For example, if you are on version 1.37 and want to get to version 1.43, we recommend that you upgrade each minor step to 1.43.

From e875078b58e52945e08771b213c5ba4dc14ef86b Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Thu, 1 Jun 2023 10:17:40 +0200
Subject: [PATCH 21/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index b798d30155..4426a13117 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -137,7 +137,7 @@ You can choose to run in-place upgrades on each node or to replace each node wit
 
 A rolling upgrade procedure might look like this:
 - Stop the first node and remove it from the load balancer.
-- Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded.
+- Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depend on the code paths being updated as well as how users interact with the system. They should be minimal.
 - Start the first node and add it back to the load balancer.
 - Stop the second and third nodes, remove them from the load balancer, and upgrade them. 
 - Start the second and third nodes and add them back to the load balancer.

From 9249695b06462aaa8eed36764c1fbe04c599fd01 Mon Sep 17 00:00:00 2001
From: Tatenda <31291528+rideam@users.noreply.github.com>
Date: Thu, 1 Jun 2023 16:29:39 +0200
Subject: [PATCH 22/55] feedback updates

---
 .../admin-guide/blue_green_upgrade.plantuml   | 22 +++++++++++++++
 .../docs/admin-guide/rolling_upgrade.plantuml | 14 ++++++++++
 .../docs/admin-guide/upgrade/blue-green.svg   | 16 -----------
 .../admin-guide/upgrade/rolling-upgrade.svg   | 16 -----------
 site/docs/v1/tech/admin-guide/upgrade.adoc    | 27 +++++++++++--------
 .../v1/tech/installation-guide/docker.adoc    |  7 +----
 .../v1/tech/installation-guide/homebrew.adoc  | 26 +-----------------
 .../v1/tech/shared/_upgrade-using-brew.adoc   | 25 +++++++++++++++++
 .../v1/tech/shared/_upgrade-using-docker.adoc |  6 +++++
 9 files changed, 85 insertions(+), 74 deletions(-)
 create mode 100644 site/_diagrams/docs/admin-guide/blue_green_upgrade.plantuml
 create mode 100644 site/_diagrams/docs/admin-guide/rolling_upgrade.plantuml
 delete mode 100644 site/assets/img/docs/admin-guide/upgrade/blue-green.svg
 delete mode 100644 site/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg
 create mode 100644 site/docs/v1/tech/shared/_upgrade-using-brew.adoc
 create mode 100644 site/docs/v1/tech/shared/_upgrade-using-docker.adoc

diff --git a/site/_diagrams/docs/admin-guide/blue_green_upgrade.plantuml b/site/_diagrams/docs/admin-guide/blue_green_upgrade.plantuml
new file mode 100644
index 0000000000..d6c99e7d6b
--- /dev/null
+++ b/site/_diagrams/docs/admin-guide/blue_green_upgrade.plantuml
@@ -0,0 +1,22 @@
+@startuml
+  !include ../../_config.plantuml
+
+actor "Users" as u
+agent "Load Balancer" as lb
+
+rectangle "Blue Deployment (old version)" as f1 {
+   [Node 1]#lightblue
+   [Node 2]#lightblue
+   [Node 3]#blue;text:white
+}
+
+rectangle "Green Deployment (new version)" as f2 {
+   [Node #1]#lightgreen
+   [Node #2]#lightgreen
+   [Node #3]#lightgreen
+}
+
+u -> lb
+lb -> f1
+lb ..> f2 : Switch traffic when ready
+@enduml
diff --git a/site/_diagrams/docs/admin-guide/rolling_upgrade.plantuml b/site/_diagrams/docs/admin-guide/rolling_upgrade.plantuml
new file mode 100644
index 0000000000..9fd2d97e1d
--- /dev/null
+++ b/site/_diagrams/docs/admin-guide/rolling_upgrade.plantuml
@@ -0,0 +1,14 @@
+@startuml
+  !include ../../_config.plantuml
+
+actor "Users" as u
+agent "Load Balancer" as lb
+component "Node 1" as n1 #lightgreen
+component "Node 2" as n2 #lightblue
+component "Node 3" as n3 #lightblue
+
+u -> lb
+lb ..> n1 : Switch traffic when ready \n (Upgrade one node at a time)
+lb --> n2
+lb -> n3
+@enduml
diff --git a/site/assets/img/docs/admin-guide/upgrade/blue-green.svg b/site/assets/img/docs/admin-guide/upgrade/blue-green.svg
deleted file mode 100644
index 5acb31122a..0000000000
--- a/site/assets/img/docs/admin-guide/upgrade/blue-green.svg
+++ /dev/null
@@ -1,16 +0,0 @@
-<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 809.0030546609328 708.1438392940221" width="1618.0061093218656" height="1416.2876785880442">
-  <!-- svg-source:excalidraw -->
-  
-  <defs>
-    <style class="style-fonts">
-      @font-face {
-        font-family: "Virgil";
-        src: url("https://excalidraw.com/Virgil.woff2");
-      }
-      @font-face {
-        font-family: "Cascadia";
-        src: url("https://excalidraw.com/Cascadia.woff2");
-      }
-    </style>
-  </defs>
-  <rect x="0" y="0" width="809.0030546609328" height="708.1438392940221" fill="#ffffff"></rect><g stroke-linecap="round" transform="translate(537.3571990951166 10) rotate(0 98.99999999999994 140)"><path d="M7.86 8.16 C7.86 8.16, 7.86 8.16, 7.86 8.16 M7.86 8.16 C7.86 8.16, 7.86 8.16, 7.86 8.16 M3.66 19.09 C9.47 15.42, 11.56 10.75, 18.1 2.48 M3.66 19.09 C7.67 14.35, 12.6 9.92, 18.1 2.48 M2.75 26.24 C8.27 18.95, 13.86 13.92, 24.4 1.33 M2.75 26.24 C7.98 19.35, 15.42 13.47, 24.4 1.33 M2.48 32.64 C10.8 23.54, 16.31 17.58, 30.7 0.18 M2.48 32.64 C12.91 20.39, 24.86 8.19, 30.7 0.18 M2.88 38.28 C13.92 23.64, 24.57 9.31, 34.37 2.05 M2.88 38.28 C15.2 26.07, 25.44 12.1, 34.37 2.05 M2.62 44.68 C11.97 34.46, 18.94 25.51, 39.36 2.41 M2.62 44.68 C15.65 29.87, 26.87 15.62, 39.36 2.41 M2.36 51.07 C19.07 32.93, 31.56 18.67, 45 2.02 M2.36 51.07 C14 39.3, 24.8 26.01, 45 2.02 M2.75 56.72 C11.42 47.44, 20.8 33.53, 49.99 2.38 M2.75 56.72 C16.6 39.35, 31.88 24.3, 49.99 2.38 M2.49 63.11 C18.61 45.76, 30.37 30.88, 55.63 1.98 M2.49 63.11 C22 40.75, 41.01 19.52, 55.63 1.98 M2.23 69.51 C23.23 48.05, 43.28 25.07, 60.62 2.34 M2.23 69.51 C17.16 51.98, 31.95 33.38, 60.62 2.34 M2.62 75.16 C18.43 57.29, 35.53 38.31, 66.26 1.95 M2.62 75.16 C16.38 60.45, 29.44 44.41, 66.26 1.95 M2.36 81.55 C30.39 52.12, 54.61 19.73, 71.25 2.31 M2.36 81.55 C18.61 63.81, 32.64 45.17, 71.25 2.31 M2.76 87.2 C24.53 60.86, 47.27 34.66, 76.89 1.91 M2.76 87.2 C18.27 68.75, 34.36 51.22, 76.89 1.91 M2.49 93.59 C21.52 72.87, 37.01 53.28, 81.88 2.27 M2.49 93.59 C29.9 63.21, 55.4 32.58, 81.88 2.27 M2.23 99.99 C31.92 64.72, 62.47 29.53, 87.52 1.88 M2.23 99.99 C31.12 66.97, 58.71 34.03, 87.52 1.88 M2.63 105.64 C30.33 73.56, 60 42.84, 92.51 2.24 M2.63 105.64 C31.23 73.35, 59.23 41.6, 92.51 2.24 M2.37 112.03 C21.63 91.55, 39.19 70.07, 97.49 2.6 M2.37 112.03 C20.67 89.69, 41.31 67.9, 97.49 2.6 M2.76 117.68 C33.89 81.93, 67.48 44.03, 103.14 2.21 M2.76 117.68 C44.79 69.72, 83.25 24.43, 103.14 2.21 M2.5 124.07 C30.25 93.76, 55.54 64.67, 108.12 2.57 M2.5 124.07 C43.9 76.2, 85.4 28.41, 108.12 2.57 M2.24 130.47 C23.94 103.44, 46.04 74.99, 113.77 2.17 M2.24 130.47 C28.59 99.78, 53.47 68.5, 113.77 2.17 M2.63 136.11 C40.84 91.94, 80.28 48.75, 118.76 2.53 M2.63 136.11 C43.28 90.67, 83.01 43.07, 118.76 2.53 M2.37 142.51 C48.32 88.64, 94.74 35.13, 124.4 2.14 M2.37 142.51 C49.6 89.23, 96.32 35.77, 124.4 2.14 M2.11 148.91 C37.12 108.39, 67.72 68.06, 129.39 2.5 M2.11 148.91 C34.23 109.56, 66.43 71.5, 129.39 2.5 M2.5 154.55 C48.3 100.9, 97.04 44.83, 135.03 2.1 M2.5 154.55 C29.7 123.05, 55.87 92.84, 135.03 2.1 M2.24 160.95 C52.21 106.29, 96.79 53.76, 140.02 2.46 M2.24 160.95 C55.53 99.2, 107.57 38.59, 140.02 2.46 M2.64 166.59 C37.37 128.24, 71.93 87.58, 145 2.82 M2.64 166.59 C53.03 107.09, 106.16 47.3, 145 2.82 M2.38 172.99 C33.38 138.8, 64.68 102.65, 150.65 2.43 M2.38 172.99 C51.92 117.41, 100.63 60.79, 150.65 2.43 M2.11 179.39 C48.77 125.78, 95.67 72.45, 155.63 2.79 M2.11 179.39 C55.53 120.01, 108.86 59.42, 155.63 2.79 M2.51 185.03 C61.39 117.14, 122.22 47.51, 161.28 2.39 M2.51 185.03 C61.79 117.77, 120.28 50.41, 161.28 2.39 M2.25 191.43 C66.49 117.79, 133.59 40.57, 166.26 2.75 M2.25 191.43 C55.66 130.45, 110.13 67.15, 166.26 2.75 M1.99 197.83 C60.02 132.39, 116.72 66.48, 173.22 0.85 M1.99 197.83 C56.53 132.65, 113.37 68.68, 173.22 0.85 M2.38 203.47 C55.8 142.54, 105.92 83.19, 177.55 1.96 M2.38 203.47 C59.82 141.49, 114.71 77.48, 177.55 1.96 M2.12 209.87 C43.53 162.4, 83.98 115.33, 181.88 3.08 M2.12 209.87 C56.68 149.81, 109.58 89.9, 181.88 3.08 M2.51 215.51 C41.77 170.26, 80.94 125.02, 185.55 4.95 M2.51 215.51 C39.85 172.79, 76.08 130.15, 185.55 4.95 M2.25 221.91 C70.63 142.11, 143.67 61.15, 188.57 7.57 M2.25 221.91 C60.76 155.88, 116.82 90.54, 188.57 7.57 M1.99 228.31 C48.27 175.49, 96.07 122.47, 191.59 10.2 M1.99 228.31 C58.61 163.46, 114.14 97.56, 191.59 10.2 M2.39 233.95 C75.53 151.15, 147.62 67.13, 194.61 12.82 M2.39 233.95 C53.67 174.26, 105.92 114.26, 194.61 12.82 M2.12 240.35 C68.62 165.51, 132.83 89.47, 196.32 16.95 M2.12 240.35 C46.63 191.53, 88.52 142.77, 196.32 16.95 M0.55 248.26 C75.78 163.4, 147.54 79.95, 198.68 20.33 M0.55 248.26 C47.69 193.69, 95.01 139.72, 198.68 20.33 M0.95 253.9 C68.72 178.23, 132.79 100.65, 199.73 25.22 M0.95 253.9 C80.67 163.74, 158.9 73.2, 199.73 25.22 M2 258.79 C76.1 172.49, 151.96 88.25, 198.81 32.37 M2 258.79 C67.85 183.56, 133.5 109.2, 198.81 32.37 M3.7 262.92 C62.42 193.75, 120.04 126.32, 198.55 38.77 M3.7 262.92 C72.98 184.17, 142.28 105.82, 198.55 38.77 M4.75 267.81 C79.93 180.18, 157.01 94.35, 198.95 44.42 M4.75 267.81 C48.64 217, 92.09 167.99, 198.95 44.42 M7.77 270.43 C50.97 221.78, 90.05 172.25, 198.69 50.81 M7.77 270.43 C54.51 218.41, 100.56 165.1, 198.69 50.81 M10.79 273.06 C60.58 216.82, 108.64 159.24, 198.42 57.21 M10.79 273.06 C55.68 218.89, 101.59 166.54, 198.42 57.21 M13.15 276.44 C69.83 214.75, 121.13 153.32, 198.82 62.85 M13.15 276.44 C68.52 212.96, 124.02 148.41, 198.82 62.85 M16.83 278.31 C54.21 235.36, 93.99 192.29, 198.56 69.25 M16.83 278.31 C67.38 218.94, 118.87 159.68, 198.56 69.25 M20.5 280.18 C62.42 232.72, 101.83 185.59, 198.95 74.89 M20.5 280.18 C89.12 200.94, 158.21 120.72, 198.95 74.89 M25.49 280.54 C80.64 213.24, 139.59 149.3, 198.69 81.29 M25.49 280.54 C76.88 221.62, 126.47 163.02, 198.69 81.29 M29.82 281.65 C93.6 204.65, 157.41 130.78, 198.43 87.69 M29.82 281.65 C77.25 228.07, 122.07 176.52, 198.43 87.69 M34.81 282.01 C77.48 232.92, 124.56 182.3, 198.82 93.33 M34.81 282.01 C96.14 213.6, 156.81 141.99, 198.82 93.33 M39.8 282.37 C102.68 208.38, 163.45 135.29, 198.56 99.73 M39.8 282.37 C90.08 224.02, 139.95 165.67, 198.56 99.73 M45.44 281.98 C99.27 218.78, 155.89 157.15, 198.96 105.37 M45.44 281.98 C90.26 230.04, 133.6 179.62, 198.96 105.37 M50.43 282.34 C100.82 222.99, 151.22 168.21, 198.69 111.77 M50.43 282.34 C80.02 245.85, 111.67 209.55, 198.69 111.77 M56.07 281.94 C97.47 232.53, 136.67 186.79, 198.43 118.17 M56.07 281.94 C107.75 222.22, 159.41 164.4, 198.43 118.17 M61.06 282.3 C112.44 222.23, 168.44 161.3, 198.83 123.81 M61.06 282.3 C94.26 245.15, 127.9 208.51, 198.83 123.81 M66.7 281.91 C93.15 250.33, 121 216.01, 198.57 130.21 M66.7 281.91 C115.93 226.14, 164.21 169.97, 198.57 130.21 M71.69 282.27 C114.27 230.43, 160.61 180.29, 198.96 135.85 M71.69 282.27 C121.02 224.06, 171.25 166.19, 198.96 135.85 M76.67 282.63 C107.03 247.99, 136.46 214.26, 198.7 142.25 M76.67 282.63 C106.53 246.7, 135.96 211.51, 198.7 142.25 M82.32 282.23 C123.89 232.95, 164.74 186.67, 198.44 148.65 M82.32 282.23 C114.69 246.04, 146.88 208.78, 198.44 148.65 M87.3 282.59 C109.54 259.35, 131.46 232.95, 198.83 154.29 M87.3 282.59 C131.7 230.13, 175.37 180.62, 198.83 154.29 M92.95 282.2 C127.75 238.63, 163.41 197.42, 198.57 160.69 M92.95 282.2 C115.01 257.21, 136.64 232.85, 198.57 160.69 M97.93 282.56 C120.02 257.39, 144.93 229.1, 198.97 166.33 M97.93 282.56 C134.92 240.37, 171.84 197.9, 198.97 166.33 M103.58 282.16 C137.81 241.12, 172.4 204.23, 198.7 172.73 M103.58 282.16 C131.83 249.39, 158.7 217.07, 198.7 172.73 M108.56 282.52 C137.86 248.42, 171.73 212.34, 198.44 179.13 M108.56 282.52 C140.01 244.82, 173.52 207.35, 198.44 179.13 M114.21 282.13 C135.24 254.26, 158.12 228.24, 198.84 184.77 M114.21 282.13 C146.15 247.55, 177.42 210.63, 198.84 184.77 M119.19 282.49 C148.23 251.61, 176.42 216.04, 198.58 191.17 M119.19 282.49 C147.52 250.02, 174.3 217.27, 198.58 191.17 M124.84 282.1 C147.03 259.35, 168.7 233.8, 198.97 196.81 M124.84 282.1 C144.77 259.42, 163.34 235.95, 198.97 196.81 M129.82 282.46 C151.22 257.84, 176.15 231.68, 198.71 203.21 M129.82 282.46 C155.28 252.85, 180.49 224.42, 198.71 203.21 M135.47 282.06 C149.27 268.79, 159.88 254.7, 198.45 209.61 M135.47 282.06 C156.33 258.52, 176.36 235.81, 198.45 209.61 M140.45 282.42 C157.34 264.11, 173.14 246.81, 198.84 215.25 M140.45 282.42 C163.96 256.11, 186.44 230.79, 198.84 215.25 M146.1 282.03 C164.16 262.4, 180.47 239.84, 198.58 221.65 M146.1 282.03 C162.25 264.45, 176.53 246.52, 198.58 221.65 M151.08 282.39 C163.86 268.72, 177.41 252.92, 198.98 227.29 M151.08 282.39 C163.42 267.88, 176.06 254.24, 198.98 227.29 M156.73 281.99 C169.04 269.04, 178.3 258.29, 198.71 233.69 M156.73 281.99 C166.15 270.65, 177.54 259.33, 198.71 233.69 M161.71 282.35 C171.43 272.88, 176.57 264.21, 198.45 240.09 M161.71 282.35 C175.74 266.05, 189.27 250.48, 198.45 240.09 M168.01 281.2 C180.76 268.15, 191.89 255.35, 198.85 245.73 M168.01 281.2 C174.73 273.43, 182.52 266.32, 198.85 245.73 M173.66 280.81 C178.85 272.79, 184.87 267.23, 200.55 249.86 M173.66 280.81 C185.08 267.62, 194.82 257.02, 200.55 249.86 M180.61 278.9 C189.51 268.48, 196.58 263.47, 199.64 257.02 M180.61 278.9 C185.55 274.24, 189.42 269.41, 199.64 257.02" stroke="#4c6ef5" stroke-width="0.5" fill="none"></path><path d="M32 0 M32 0 C60.97 -3.14, 90.58 -2.55, 166 0 M32 0 C76.83 1.29, 120.82 1.12, 166 0 M166 0 C187.41 0.97, 197.42 10.16, 198 32 M166 0 C188.97 0.1, 199.17 12.86, 198 32 M198 32 C199.24 103.34, 198.47 174.44, 198 248 M198 32 C198.88 116.47, 199.05 201.51, 198 248 M198 248 C199.14 267.7, 185.59 278.1, 166 280 M198 248 C199.11 271.41, 187.81 280.49, 166 280 M166 280 C127.86 279.76, 89.29 281.35, 32 280 M166 280 C126.54 279.31, 85.04 278.49, 32 280 M32 280 C12.35 281.02, 1.87 267.66, 0 248 M32 280 C9.78 277.91, -0.05 271.06, 0 248 M0 248 C-0.3 177.86, 0.8 105.38, 0 32 M0 248 C-1.07 195.89, 0.46 144.56, 0 32 M0 32 C0.35 9.97, 11.54 0.35, 32 0 M0 32 C-0.3 12.12, 9.54 1.3, 32 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g stroke-linecap="round" transform="translate(557.3571990951166 41.306603130202745) rotate(0 78 23)"><path d="M10.72 -1 L148.98 -0.45 L154.2 2.18 L157.02 6.91 L153.74 39.99 L151.8 45.27 L144.82 44.85 L8.07 45.69 L4.86 45.12 L1.56 37.22 L-0.7 7.41 L4.09 2.13 L13.21 0.53" stroke="none" stroke-width="0" fill="#228be6"></path><path d="M11.5 0 M11.5 0 C38.91 -2.04, 64.2 -1.05, 144.5 0 M11.5 0 C47.63 2.2, 84.09 1.31, 144.5 0 M144.5 0 C153 0.75, 154.41 3.62, 156 11.5 M144.5 0 C150.81 1.63, 154.8 3.13, 156 11.5 M156 11.5 C155.72 19.13, 156.84 22.74, 156 34.5 M156 11.5 C156.94 19.51, 155.89 28.32, 156 34.5 M156 34.5 C154.5 42.84, 152.74 45.23, 144.5 46 M156 34.5 C157.69 40.71, 151.89 44.01, 144.5 46 M144.5 46 C101.92 45.42, 61.9 47.03, 11.5 46 M144.5 46 C102.31 45.83, 60.12 46.64, 11.5 46 M11.5 46 C1.84 47.89, -1.2 43.4, 0 34.5 M11.5 46 C4.84 45.69, 1.52 39.9, 0 34.5 M0 34.5 C0.39 28.88, 0.88 21.37, 0 11.5 M0 34.5 C0.27 28.87, -0.42 23.44, 0 11.5 M0 11.5 C-1.95 5.83, 5.53 -1.75, 11.5 0 M0 11.5 C-1.7 3.61, 2.56 -1.11, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(604.5072006209955 51.806603130202745) rotate(0 30.849998474121094 12.5)"><text x="30.849998474121094" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 1</text></g><g stroke-linecap="round" transform="translate(557.3571990951166 106) rotate(0 78 23)"><path d="M10.89 -0.49 L150.3 0.95 L152.76 4.18 L156.57 7.38 L156.56 40.49 L149.96 46.05 L143.77 45.57 L6.61 43.79 L3.54 43.7 L-0.59 38.66 L-1.09 8.57 L1.15 3.13 L10.34 -0.74" stroke="none" stroke-width="0" fill="#228be6"></path><path d="M11.5 0 M11.5 0 C46.29 -0.08, 76.88 -0.77, 144.5 0 M11.5 0 C48.26 -0.18, 84.15 0.21, 144.5 0 M144.5 0 C153.4 0.88, 155.73 5.16, 156 11.5 M144.5 0 C149.9 -0.17, 157.4 1.68, 156 11.5 M156 11.5 C156.45 18.25, 155.32 25.47, 156 34.5 M156 11.5 C157.08 17.84, 157.09 26.98, 156 34.5 M156 34.5 C154.25 40.69, 151.97 44.89, 144.5 46 M156 34.5 C154.89 40.17, 153.7 44.26, 144.5 46 M144.5 46 C98.1 46.34, 52.49 46.04, 11.5 46 M144.5 46 C117.35 45.72, 88.24 45.16, 11.5 46 M11.5 46 C2.28 45.03, -1.25 43.37, 0 34.5 M11.5 46 C4.74 47.46, 0.49 39.94, 0 34.5 M0 34.5 C-0.84 27.71, -0.81 23.46, 0 11.5 M0 34.5 C-0.02 28.06, 0.85 20.71, 0 11.5 M0 11.5 C-0.69 5.5, 4.19 -0.09, 11.5 0 M0 11.5 C-0.65 3.68, 2.79 0.18, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(600.0972007735834 116.5) rotate(0 35.2599983215332 12.5)"><text x="35.2599983215332" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 2</text></g><g stroke-linecap="round" transform="translate(559.3571990951166 184) rotate(0 78 23)"><path d="M12.38 -0.27 L150.86 -1.25 L152.97 4.09 L153.95 9.34 L156.39 40.55 L151.83 43.62 L143.7 44.95 L6.83 46.07 L1.86 45.11 L-1.77 39.19 L1.87 7.05 L1.39 2.68 L10.39 -0.97" stroke="none" stroke-width="0" fill="#4c6ef5"></path><path d="M11.5 0 M11.5 0 C40.64 0.12, 70.07 -0.26, 144.5 0 M11.5 0 C44.52 0.16, 78.4 1.67, 144.5 0 M144.5 0 C154.05 -0.41, 156.75 2.28, 156 11.5 M144.5 0 C151.05 -1.44, 157.38 4.74, 156 11.5 M156 11.5 C154.86 20.42, 154.06 27.44, 156 34.5 M156 11.5 C155.89 17.42, 155.91 22.49, 156 34.5 M156 34.5 C156.78 44.08, 151.92 45.31, 144.5 46 M156 34.5 C157.91 42.57, 152.07 45.35, 144.5 46 M144.5 46 C107.19 46.1, 65.61 46.61, 11.5 46 M144.5 46 C101.42 47.6, 59.59 47.94, 11.5 46 M11.5 46 C3.24 44.34, -1.77 41.33, 0 34.5 M11.5 46 C5.83 48.23, 1.22 41.43, 0 34.5 M0 34.5 C0.27 29.09, -0.74 22.11, 0 11.5 M0 34.5 C0.45 25.61, 0.79 16.48, 0 11.5 M0 11.5 C-0.69 3.83, 4.71 -1.26, 11.5 0 M0 11.5 C-2.25 6.05, 2.09 -1.45, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(602.4071983321771 194.5) rotate(0 34.95000076293945 12.5)"><text x="34.95000076293945" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 3</text></g><g stroke-linecap="round" transform="translate(544.8525020588318 375.10610387388687) rotate(0 98.99999999999994 140)"><path d="M7.86 8.16 C7.86 8.16, 7.86 8.16, 7.86 8.16 M7.86 8.16 C7.86 8.16, 7.86 8.16, 7.86 8.16 M3.66 19.09 C7.37 14.35, 11.74 5.67, 18.1 2.48 M3.66 19.09 C6.85 15.7, 12.15 10.87, 18.1 2.48 M2.75 26.24 C10.93 19.97, 17.03 11.58, 24.4 1.33 M2.75 26.24 C8.9 19.35, 15.84 12.02, 24.4 1.33 M2.48 32.64 C13.67 21.65, 23.31 10.05, 30.7 0.18 M2.48 32.64 C9.72 25.66, 16 17.56, 30.7 0.18 M2.88 38.28 C9.84 25.71, 21.38 18.04, 34.37 2.05 M2.88 38.28 C14.24 26.03, 25.12 11.81, 34.37 2.05 M2.62 44.68 C14.06 29.3, 27.86 16.43, 39.36 2.41 M2.62 44.68 C17.78 28.7, 32.67 10.98, 39.36 2.41 M2.36 51.07 C9.93 39.22, 20.43 27.56, 45 2.02 M2.36 51.07 C11.76 40.62, 20.55 31.42, 45 2.02 M2.75 56.72 C13.72 42.46, 27.89 25.38, 49.99 2.38 M2.75 56.72 C14.13 45.17, 25.39 31.34, 49.99 2.38 M2.49 63.11 C19.26 44.97, 35.8 22.97, 55.63 1.98 M2.49 63.11 C19.31 43.38, 35.34 24.51, 55.63 1.98 M2.23 69.51 C18.25 52.84, 35.05 31.42, 60.62 2.34 M2.23 69.51 C17.58 52.18, 33.64 33.42, 60.62 2.34 M2.62 75.16 C17.1 56.2, 31.96 40.07, 66.26 1.95 M2.62 75.16 C24.48 49.07, 46.3 23.85, 66.26 1.95 M2.36 81.55 C24.32 57.79, 41.68 33.55, 71.25 2.31 M2.36 81.55 C15.75 64.77, 30.49 48.43, 71.25 2.31 M2.76 87.2 C29.53 53.35, 58.71 21.02, 76.89 1.91 M2.76 87.2 C27.47 60.52, 50.01 33.66, 76.89 1.91 M2.49 93.59 C30.39 65.92, 54.94 33, 81.88 2.27 M2.49 93.59 C19.28 75.21, 36.25 56.86, 81.88 2.27 M2.23 99.99 C23.47 75.19, 45.61 48.82, 87.52 1.88 M2.23 99.99 C22.38 77.81, 39.72 56.44, 87.52 1.88 M2.63 105.64 C25.5 82.44, 48.33 53.24, 92.51 2.24 M2.63 105.64 C38.04 65.49, 73.72 25.11, 92.51 2.24 M2.37 112.03 C25.17 83.35, 50.79 57.74, 97.49 2.6 M2.37 112.03 C39.54 68.97, 76.47 26.61, 97.49 2.6 M2.76 117.68 C38.94 76.22, 76.83 30.72, 103.14 2.21 M2.76 117.68 C38.82 74.53, 76.12 32.17, 103.14 2.21 M2.5 124.07 C31.59 89.36, 57.94 58.92, 108.12 2.57 M2.5 124.07 C41.21 81.41, 78.58 36.8, 108.12 2.57 M2.24 130.47 C34.04 93.57, 62.41 56.01, 113.77 2.17 M2.24 130.47 C36.42 94.1, 68.39 55.28, 113.77 2.17 M2.63 136.11 C43.01 85.76, 88 40.56, 118.76 2.53 M2.63 136.11 C47.05 83.02, 94.87 29.48, 118.76 2.53 M2.37 142.51 C27.97 114.49, 50.4 83.34, 124.4 2.14 M2.37 142.51 C27.98 112.73, 53.54 82.18, 124.4 2.14 M2.11 148.91 C28.27 113.95, 58.41 81.99, 129.39 2.5 M2.11 148.91 C51.53 93.32, 99.37 35.95, 129.39 2.5 M2.5 154.55 C37.96 116.01, 69.1 77.68, 135.03 2.1 M2.5 154.55 C46.03 104.9, 87.64 57.17, 135.03 2.1 M2.24 160.95 C49.78 108.83, 92.64 54.5, 140.02 2.46 M2.24 160.95 C44.78 111.21, 87.51 61.62, 140.02 2.46 M2.64 166.59 C52.97 104.32, 106.95 46.64, 145 2.82 M2.64 166.59 C41.43 122.57, 80.3 79.07, 145 2.82 M2.38 172.99 C62.61 105.17, 120.48 38.67, 150.65 2.43 M2.38 172.99 C31.54 139.31, 61.63 104.74, 150.65 2.43 M2.11 179.39 C58.34 110.78, 116.42 45.38, 155.63 2.79 M2.11 179.39 C49.58 123.4, 97.32 68.22, 155.63 2.79 M2.51 185.03 C47.71 132.9, 93.59 79.99, 161.28 2.39 M2.51 185.03 C63.09 116.45, 121.61 47.65, 161.28 2.39 M2.25 191.43 C54.89 130.67, 106.18 69.33, 166.26 2.75 M2.25 191.43 C59.06 126.45, 116.47 61.17, 166.26 2.75 M1.99 197.83 C61.37 129.24, 123.56 60.44, 173.22 0.85 M1.99 197.83 C65.31 123.61, 128.63 48.94, 173.22 0.85 M2.38 203.47 C64.13 130.86, 124.45 59.09, 177.55 1.96 M2.38 203.47 C44.37 156.92, 85.37 109.62, 177.55 1.96 M2.12 209.87 C52.26 153.8, 101.33 99.65, 181.88 3.08 M2.12 209.87 C50.78 152.22, 100.97 94.69, 181.88 3.08 M2.51 215.51 C44.66 166.28, 86.22 117.21, 185.55 4.95 M2.51 215.51 C60.5 149.19, 117.81 81.87, 185.55 4.95 M2.25 221.91 C39.08 176.07, 78.86 134.24, 188.57 7.57 M2.25 221.91 C68.6 143.96, 135.36 67.59, 188.57 7.57 M1.99 228.31 C46.16 175.35, 89.44 124.44, 191.59 10.2 M1.99 228.31 C55.98 165.6, 112.56 101.78, 191.59 10.2 M2.39 233.95 C50.83 176.7, 102.68 118.92, 194.61 12.82 M2.39 233.95 C44.07 185.26, 86.21 135.6, 194.61 12.82 M2.12 240.35 C44.22 192, 88.35 143.4, 196.32 16.95 M2.12 240.35 C68.01 165.73, 133.04 90.01, 196.32 16.95 M0.55 248.26 C40.14 202.06, 81.26 157.82, 198.68 20.33 M0.55 248.26 C54.62 185.21, 108.56 122.43, 198.68 20.33 M0.95 253.9 C77.34 167.96, 153.81 79.95, 199.73 25.22 M0.95 253.9 C76.11 166.8, 151.8 79.46, 199.73 25.22 M2 258.79 C73.17 179.79, 142.85 99.3, 198.81 32.37 M2 258.79 C50.49 201.09, 101.28 142.66, 198.81 32.37 M3.7 262.92 C62.02 195.81, 121.31 127.1, 198.55 38.77 M3.7 262.92 C48.7 211.31, 94.56 158.13, 198.55 38.77 M4.75 267.81 C63.9 200.31, 124.53 132.56, 198.95 44.42 M4.75 267.81 C66.6 196.18, 128.37 125.43, 198.95 44.42 M7.77 270.43 C63.06 209.59, 117.34 145.88, 198.69 50.81 M7.77 270.43 C59.43 212.59, 109.81 155.61, 198.69 50.81 M10.79 273.06 C83.83 191.97, 156.42 106.57, 198.42 57.21 M10.79 273.06 C69.83 203.55, 130.55 133.49, 198.42 57.21 M13.15 276.44 C57.96 225.93, 101.7 174.36, 198.82 62.85 M13.15 276.44 C72.48 210.02, 130.35 144.13, 198.82 62.85 M16.83 278.31 C90.61 195.12, 161.23 112.14, 198.56 69.25 M16.83 278.31 C81.66 203.7, 145.86 127.65, 198.56 69.25 M20.5 280.18 C87.12 202.87, 152.2 125.23, 198.95 74.89 M20.5 280.18 C90.59 202.9, 158.72 124.09, 198.95 74.89 M25.49 280.54 C78.81 223.04, 126.45 165.7, 198.69 81.29 M25.49 280.54 C64.33 234.28, 105.04 188.2, 198.69 81.29 M29.82 281.65 C82.71 219.13, 137.75 158.15, 198.43 87.69 M29.82 281.65 C87.8 212.89, 146.94 145.23, 198.43 87.69 M34.81 282.01 C82.24 225.03, 129.4 171.42, 198.82 93.33 M34.81 282.01 C92.45 214.19, 150.02 148.94, 198.82 93.33 M39.8 282.37 C101.17 210.87, 164.22 139.35, 198.56 99.73 M39.8 282.37 C80.99 235.89, 120.78 189.35, 198.56 99.73 M45.44 281.98 C101.43 220.88, 155.78 156.27, 198.96 105.37 M45.44 281.98 C87.55 236.1, 127.44 190.26, 198.96 105.37 M50.43 282.34 C99.06 222.99, 148.94 166.8, 198.69 111.77 M50.43 282.34 C81.43 246.68, 110.67 212.1, 198.69 111.77 M56.07 281.94 C100.59 230.16, 146.24 178.38, 198.43 118.17 M56.07 281.94 C101.19 230.23, 145.01 180.42, 198.43 118.17 M61.06 282.3 C114.26 218.61, 169.79 155.67, 198.83 123.81 M61.06 282.3 C99.01 238.62, 135.05 194.71, 198.83 123.81 M66.7 281.91 C114.12 226.8, 164.14 172.95, 198.57 130.21 M66.7 281.91 C117.19 224.83, 167.08 166.29, 198.57 130.21 M71.69 282.27 C99.7 249.29, 131.55 217.94, 198.96 135.85 M71.69 282.27 C121.95 224.9, 173.56 165.33, 198.96 135.85 M76.67 282.63 C119.36 236, 163.28 185.67, 198.7 142.25 M76.67 282.63 C117.01 234.97, 159.05 187.81, 198.7 142.25 M82.32 282.23 C125.47 231.41, 168.67 179.9, 198.44 148.65 M82.32 282.23 C117.36 242.14, 151.89 201.62, 198.44 148.65 M87.3 282.59 C115.34 249.27, 142.89 215.75, 198.83 154.29 M87.3 282.59 C109.34 253.83, 133.62 227.54, 198.83 154.29 M92.95 282.2 C118.61 254.48, 144.65 223.52, 198.57 160.69 M92.95 282.2 C130.83 239.55, 166.83 197.48, 198.57 160.69 M97.93 282.56 C134.27 240.51, 171.7 197.9, 198.97 166.33 M97.93 282.56 C118.08 257.77, 138.91 235.01, 198.97 166.33 M103.58 282.16 C129.18 252.07, 158.4 222.55, 198.7 172.73 M103.58 282.16 C129.24 251.76, 155.24 221.31, 198.7 172.73 M108.56 282.52 C132.62 252.61, 158.05 222.53, 198.44 179.13 M108.56 282.52 C132.51 253.97, 158.55 225.87, 198.44 179.13 M114.21 282.13 C147.28 244.68, 175.91 209.14, 198.84 184.77 M114.21 282.13 C141.67 252.23, 166.3 220.69, 198.84 184.77 M119.19 282.49 C143.54 255.94, 165.21 230.87, 198.58 191.17 M119.19 282.49 C147.42 249.79, 177.55 215.44, 198.58 191.17 M124.84 282.1 C149.92 254.54, 173.1 226.45, 198.97 196.81 M124.84 282.1 C141.46 263.33, 157.97 245.67, 198.97 196.81 M129.82 282.46 C142.74 264.3, 157.18 251.87, 198.71 203.21 M129.82 282.46 C154.96 255.65, 179.5 225.52, 198.71 203.21 M135.47 282.06 C156.25 258.62, 175.52 235.74, 198.45 209.61 M135.47 282.06 C150.55 264.61, 167.27 245.19, 198.45 209.61 M140.45 282.42 C161.5 261.19, 180.47 236.06, 198.84 215.25 M140.45 282.42 C159.24 260.6, 179.54 238.2, 198.84 215.25 M146.1 282.03 C160.31 266.2, 173.33 248.34, 198.58 221.65 M146.1 282.03 C157.06 268.96, 170.08 253.81, 198.58 221.65 M151.08 282.39 C166.37 263.85, 182.9 248.22, 198.98 227.29 M151.08 282.39 C166.8 265.82, 180.98 247.19, 198.98 227.29 M156.73 281.99 C171.22 269.03, 180.74 251.24, 198.71 233.69 M156.73 281.99 C165.78 271.22, 175.2 260.93, 198.71 233.69 M161.71 282.35 C173.17 272.32, 182.23 258.46, 198.45 240.09 M161.71 282.35 C174.11 268.47, 184.63 256.52, 198.45 240.09 M168.01 281.2 C176.3 272.36, 181.24 264.01, 198.85 245.73 M168.01 281.2 C177.02 272.98, 184.04 262.29, 198.85 245.73 M173.66 280.81 C181.83 271.81, 188.42 262.71, 200.55 249.86 M173.66 280.81 C180.71 273.09, 187.4 263.03, 200.55 249.86 M180.61 278.9 C186.07 271.9, 190.46 265.3, 199.64 257.02 M180.61 278.9 C185.49 272.29, 191.33 265.86, 199.64 257.02" stroke="#40c057" stroke-width="0.5" fill="none"></path><path d="M32 0 M32 0 C62.44 -1.16, 89.7 -1.68, 166 0 M32 0 C81.72 0.91, 129.04 2.11, 166 0 M166 0 C185.8 -1.72, 198.37 9.01, 198 32 M166 0 C186.7 0.62, 196.86 11.79, 198 32 M198 32 C198.63 114.47, 197.99 199.32, 198 248 M198 32 C196.3 85.96, 197.69 140.17, 198 248 M198 248 C199.45 268.85, 186.48 281.46, 166 280 M198 248 C197.49 268.18, 188.87 278.14, 166 280 M166 280 C130.8 279.09, 97.15 277.98, 32 280 M166 280 C127.7 280.25, 89.83 280.19, 32 280 M32 280 C8.74 279.7, 1.89 269.47, 0 248 M32 280 C10.46 278.81, -2.22 268.56, 0 248 M0 248 C-1.74 170.77, -1.7 92, 0 32 M0 248 C-1.58 189.94, -1.36 133.09, 0 32 M0 32 C-0.4 11.4, 11.4 -0.82, 32 0 M0 32 C1.51 11.82, 12.12 -1.05, 32 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g stroke-linecap="round" transform="translate(564.8525020588318 398.10610387388687) rotate(0 78 23)"><path d="M11.14 1.41 L150.76 1.76 L154.27 3.15 L156.38 9.92 L155.74 37.68 L150.86 44.26 L145.42 45.99 L6.22 43.99 L3.87 41.21 L-1.76 36.52 L0.48 6.89 L1.6 4.68 L13.14 0.98" stroke="none" stroke-width="0" fill="#40c057"></path><path d="M11.5 0 M11.5 0 C55.01 1.15, 96.63 0.7, 144.5 0 M11.5 0 C51.63 1.74, 92.57 2.01, 144.5 0 M144.5 0 C153.66 -1.77, 156.55 4.17, 156 11.5 M144.5 0 C153.59 -0.67, 158.06 2.17, 156 11.5 M156 11.5 C156.66 16.83, 155.23 20.58, 156 34.5 M156 11.5 C155.26 20.45, 156.71 29.54, 156 34.5 M156 34.5 C156.13 40.8, 152.55 46.81, 144.5 46 M156 34.5 C155.73 39.99, 152.9 44.79, 144.5 46 M144.5 46 C108.81 44.74, 73.78 44.97, 11.5 46 M144.5 46 C103.35 47.03, 59.71 47.9, 11.5 46 M11.5 46 C2.01 44.24, -1.07 41.19, 0 34.5 M11.5 46 C2.05 43.81, -0.72 42.23, 0 34.5 M0 34.5 C0.99 25.93, 0.86 18.02, 0 11.5 M0 34.5 C-0.79 29.1, -0.88 24.27, 0 11.5 M0 11.5 C-0.44 5.77, 3.59 -0.05, 11.5 0 M0 11.5 C0.6 5.44, 2.66 -0.16, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(612.0025035847106 408.60610387388687) rotate(0 30.849998474121094 12.5)"><text x="30.849998474121094" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 1</text></g><g stroke-linecap="round" transform="translate(563.8525020588318 471.10610387388687) rotate(0 78 23)"><path d="M12.64 0.28 L150.09 1.83 L153.59 1.03 L155.17 8.68 L156.2 39.52 L151.26 43.09 L145.49 44.08 L4.53 44.61 L3.18 41.21 L-1.09 39 L1.82 9.79 L3.25 1.41 L12.45 1.1" stroke="none" stroke-width="0" fill="#40c057"></path><path d="M11.5 0 M11.5 0 C63.35 -1.03, 113.15 -1.84, 144.5 0 M11.5 0 C59.01 -1.93, 105.3 -0.88, 144.5 0 M144.5 0 C153.41 -0.58, 157.79 2.38, 156 11.5 M144.5 0 C149.89 -0.42, 157.13 4.64, 156 11.5 M156 11.5 C157.52 20.56, 153.98 25.14, 156 34.5 M156 11.5 C156.19 18.19, 156.32 26.66, 156 34.5 M156 34.5 C155.77 40.28, 152.8 44.95, 144.5 46 M156 34.5 C155.38 41.05, 150.5 46.73, 144.5 46 M144.5 46 C106.9 47.09, 70.36 47.72, 11.5 46 M144.5 46 C104.97 46.14, 66.74 46.53, 11.5 46 M11.5 46 C2.28 44.1, -0.63 42.22, 0 34.5 M11.5 46 C5.02 45.1, 1.32 43.2, 0 34.5 M0 34.5 C-1.95 28.82, -0.81 20.39, 0 11.5 M0 34.5 C-0.03 30.03, 0.06 23.6, 0 11.5 M0 11.5 C0.52 5.23, 2.82 -0.14, 11.5 0 M0 11.5 C1.75 2.78, 3.21 0.28, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(606.5925037372984 481.60610387388687) rotate(0 35.2599983215332 12.5)"><text x="35.2599983215332" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 2</text></g><g stroke-linecap="round" transform="translate(566.8525020588318 549.1061038738869) rotate(0 78 23)"><path d="M11.96 -1.85 L148.88 0.59 L154.05 2.86 L155.57 7.51 L156.27 37.62 L149.56 43.71 L144.8 44.09 L5.2 47.08 L4.52 44.11 L0.56 35.73 L1.13 9.9 L4.66 3.17 L12.84 0.11" stroke="none" stroke-width="0" fill="#40c057"></path><path d="M11.5 0 M11.5 0 C51.51 0.34, 91.04 2.12, 144.5 0 M11.5 0 C40.27 -0.51, 68.7 -0.95, 144.5 0 M144.5 0 C150.18 -0.37, 156.98 4.54, 156 11.5 M144.5 0 C152.98 -0.84, 155.81 5.68, 156 11.5 M156 11.5 C156.19 21.06, 156.88 28.52, 156 34.5 M156 11.5 C155.93 15.88, 156.36 21.63, 156 34.5 M156 34.5 C155.46 41.2, 150.71 46.64, 144.5 46 M156 34.5 C155.66 44.39, 152.09 46.37, 144.5 46 M144.5 46 C96.88 45.73, 51.18 45.35, 11.5 46 M144.5 46 C115.56 44.4, 87.85 45.38, 11.5 46 M11.5 46 C4.86 45.22, 1.15 43.07, 0 34.5 M11.5 46 C3.28 46.89, -0.35 40.03, 0 34.5 M0 34.5 C-1.19 25.22, -1.31 18.72, 0 11.5 M0 34.5 C0.29 26.07, -0.48 16.18, 0 11.5 M0 11.5 C1.52 2.91, 3.29 0.24, 11.5 0 M0 11.5 C-1.42 3.03, 3.51 -1.93, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(609.9025012958922 559.6061038738869) rotate(0 34.95000076293945 12.5)"><text x="34.95000076293945" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 3</text></g><g transform="translate(482.36663863335957 307.7688677100676) rotate(0 143.45001220703125 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Blue Deployment (old version)</text></g><g transform="translate(493.8630705300734 673.1438392940221) rotate(0 152.5699920654297 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Green Deployment (new version)</text></g><g stroke-linecap="round" transform="translate(168.09205930249547 272.71919600358564) rotate(269.9999999999999 130.8289993006931 40.14858179597991)"><path d="M20.62 -0.99 L242.56 1.67 L251.23 0.34 L256.43 4.59 L260.41 17.24 L260.68 58.98 L258.73 67.8 L253.11 79.46 L240.76 81.74 L19.59 79.45 L12.75 78.6 L1.82 73.79 L-1.3 63.96 L-0.33 14.13 L3.53 4.93 L9.86 0.06 L19.79 -1.58" stroke="none" stroke-width="0" fill="#ced4da"></path><path d="M20.07 0 M20.07 0 C97.64 -0.04, 171.98 0.45, 241.58 0 M20.07 0 C107.05 -0.67, 194.62 0.72, 241.58 0 M241.58 0 C255.3 -1.74, 260.03 8.3, 261.66 20.07 M241.58 0 C253.14 1.67, 260.87 7.97, 261.66 20.07 M261.66 20.07 C260.7 34.31, 261.02 49.55, 261.66 60.22 M261.66 20.07 C261.99 34.23, 261.04 46.9, 261.66 60.22 M261.66 60.22 C260.39 75.42, 255.89 78.39, 241.58 80.3 M261.66 60.22 C261.29 71.86, 256.53 78.98, 241.58 80.3 M241.58 80.3 C153.48 80.48, 65.79 80.02, 20.07 80.3 M241.58 80.3 C158.48 79.89, 74.7 79.31, 20.07 80.3 M20.07 80.3 C6.3 78.47, -1.88 73.58, 0 60.22 M20.07 80.3 C6.9 78.51, -1.8 73.81, 0 60.22 M0 60.22 C1.21 44.93, 0.86 28.53, 0 20.07 M0 60.22 C0.45 44.42, -0.43 30.76, 0 20.07 M0 20.07 C-0.44 4.81, 6.48 -1.4, 20.07 0 M0 20.07 C-0.13 5.89, 6.26 1.99, 20.07 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(227.33105463590343 300.36777779956554) rotate(269.9999999999999 71.59000396728516 12.5)"><text x="71.59000396728516" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Load Balancer</text></g><g transform="translate(23.299615479656893 338.1510010318354) rotate(0 28.5 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Users</text></g><g stroke-linecap="round" transform="translate(63.74243241887635 270.8911576974985) rotate(0 9.875171816384778 8.640775339336718)"><path d="M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.98 14.51 C7 9.89, 11.02 5.26, 14.13 1.68 M2.98 14.51 C6.2 10.8, 9.43 7.09, 14.13 1.68 M10.33 18.25 C12.75 15.46, 15.18 12.67, 19.51 7.69 M10.33 18.25 C12.65 15.58, 14.97 12.91, 19.51 7.69 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M15.81 15.34 C12.05 12.07, 8.29 8.8, 2.23 3.53 M15.81 15.34 C13.07 12.95, 10.32 10.56, 2.23 3.53 M20.31 8.65 C17.79 6.46, 15.27 4.27, 9.74 -0.54 M20.31 8.65 C16.35 5.21, 12.4 1.77, 9.74 -0.54" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M19.75 8.64 C19.75 9.14, 19.7 9.65, 19.6 10.14 C19.5 10.63, 19.35 11.13, 19.15 11.6 C18.96 12.07, 18.71 12.53, 18.43 12.96 C18.14 13.39, 17.81 13.81, 17.44 14.19 C17.07 14.58, 16.66 14.94, 16.22 15.26 C15.78 15.58, 15.31 15.87, 14.81 16.12 C14.32 16.37, 13.79 16.59, 13.25 16.76 C12.72 16.93, 12.15 17.06, 11.59 17.15 C11.03 17.24, 10.45 17.28, 9.88 17.28 C9.3 17.28, 8.72 17.24, 8.16 17.15 C7.6 17.06, 7.03 16.93, 6.5 16.76 C5.96 16.59, 5.43 16.37, 4.94 16.12 C4.44 15.87, 3.97 15.58, 3.53 15.26 C3.09 14.94, 2.68 14.58, 2.31 14.19 C1.94 13.81, 1.61 13.39, 1.32 12.96 C1.04 12.53, 0.79 12.07, 0.6 11.6 C0.4 11.13, 0.25 10.63, 0.15 10.14 C0.05 9.65, 0 9.14, 0 8.64 C0 8.14, 0.05 7.63, 0.15 7.14 C0.25 6.65, 0.4 6.16, 0.6 5.69 C0.79 5.22, 1.04 4.75, 1.32 4.32 C1.61 3.89, 1.94 3.47, 2.31 3.09 C2.68 2.7, 3.09 2.34, 3.53 2.02 C3.97 1.7, 4.44 1.41, 4.94 1.16 C5.43 0.91, 5.96 0.69, 6.5 0.52 C7.03 0.35, 7.6 0.22, 8.16 0.13 C8.72 0.04, 9.3 0, 9.88 0 C10.45 0, 11.03 0.04, 11.59 0.13 C12.15 0.22, 12.72 0.35, 13.25 0.52 C13.79 0.69, 14.32 0.91, 14.81 1.16 C15.31 1.41, 15.78 1.7, 16.22 2.02 C16.66 2.34, 17.07 2.7, 17.44 3.09 C17.81 3.47, 18.14 3.89, 18.43 4.32 C18.71 4.75, 18.96 5.22, 19.15 5.69 C19.35 6.16, 19.5 6.65, 19.6 7.14 C19.7 7.63, 19.73 8.39, 19.75 8.64 C19.78 8.89, 19.78 8.39, 19.75 8.64" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round" transform="translate(20.558758294554224 271.4742254811326) rotate(0 9.875171816384778 8.640775339336718)"><path d="M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.98 14.51 C7.15 9.71, 11.33 4.91, 14.13 1.68 M2.98 14.51 C6.26 10.74, 9.55 6.96, 14.13 1.68 M10.33 18.25 C13.34 14.78, 16.36 11.31, 19.51 7.69 M10.33 18.25 C13.27 14.87, 16.22 11.48, 19.51 7.69 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M15.81 15.34 C10.5 10.72, 5.18 6.1, 2.23 3.53 M15.81 15.34 C11.06 11.21, 6.31 7.08, 2.23 3.53 M20.31 8.65 C18 6.64, 15.7 4.64, 9.74 -0.54 M20.31 8.65 C17.52 6.23, 14.74 3.8, 9.74 -0.54" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M19.75 8.64 C19.75 9.14, 19.7 9.65, 19.6 10.14 C19.5 10.63, 19.35 11.13, 19.15 11.6 C18.96 12.07, 18.71 12.53, 18.43 12.96 C18.14 13.39, 17.81 13.81, 17.44 14.19 C17.07 14.58, 16.66 14.94, 16.22 15.26 C15.78 15.58, 15.31 15.87, 14.81 16.12 C14.32 16.37, 13.79 16.59, 13.25 16.76 C12.72 16.93, 12.15 17.06, 11.59 17.15 C11.03 17.24, 10.45 17.28, 9.88 17.28 C9.3 17.28, 8.72 17.24, 8.16 17.15 C7.6 17.06, 7.03 16.93, 6.5 16.76 C5.96 16.59, 5.43 16.37, 4.94 16.12 C4.44 15.87, 3.97 15.58, 3.53 15.26 C3.09 14.94, 2.68 14.58, 2.31 14.19 C1.94 13.81, 1.61 13.39, 1.32 12.96 C1.04 12.53, 0.79 12.07, 0.6 11.6 C0.4 11.13, 0.25 10.63, 0.15 10.14 C0.05 9.65, 0 9.14, 0 8.64 C0 8.14, 0.05 7.63, 0.15 7.14 C0.25 6.65, 0.4 6.16, 0.6 5.69 C0.79 5.22, 1.04 4.75, 1.32 4.32 C1.61 3.89, 1.94 3.47, 2.31 3.09 C2.68 2.7, 3.09 2.34, 3.53 2.02 C3.97 1.7, 4.44 1.41, 4.94 1.16 C5.43 0.91, 5.96 0.69, 6.5 0.52 C7.03 0.35, 7.6 0.22, 8.16 0.13 C8.72 0.04, 9.3 0, 9.88 0 C10.45 0, 11.03 0.04, 11.59 0.13 C12.15 0.22, 12.72 0.35, 13.25 0.52 C13.79 0.69, 14.32 0.91, 14.81 1.16 C15.31 1.41, 15.78 1.7, 16.22 2.02 C16.66 2.34, 17.07 2.7, 17.44 3.09 C17.81 3.47, 18.14 3.89, 18.43 4.32 C18.71 4.75, 18.96 5.22, 19.15 5.69 C19.35 6.16, 19.5 6.65, 19.6 7.14 C19.7 7.63, 19.73 8.39, 19.75 8.64 C19.78 8.89, 19.78 8.39, 19.75 8.64" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round"><g transform="translate(31.01057830181864 330.4052612187822) rotate(0 21.90843989373377 -18.494048425191174)" fill-rule="evenodd"><path d="M11.93 -33.36 C11.93 -33.36, 11.93 -33.36, 11.93 -33.36 M11.93 -33.36 C11.93 -33.36, 11.93 -33.36, 11.93 -33.36 M6.81 -15.28 C13.91 -23.45, 21.01 -31.62, 25.18 -36.41 M6.81 -15.28 C12.41 -21.72, 18 -28.16, 25.18 -36.41 M2.35 2.04 C13.9 -11.24, 25.44 -24.52, 31.87 -31.92 M2.35 2.04 C10.27 -7.07, 18.19 -16.17, 31.87 -31.92 M12.98 2.01 C20.25 -6.35, 27.52 -14.71, 37.25 -25.92 M12.98 2.01 C18.57 -4.42, 24.16 -10.85, 37.25 -25.92 M23.61 1.97 C27.65 -2.68, 31.7 -7.33, 41.32 -18.4 M23.61 1.97 C29.7 -5.03, 35.8 -12.04, 41.32 -18.4 M34.9 1.19 C37.26 -1.53, 39.62 -4.24, 46.05 -11.64 M34.9 1.19 C37.89 -2.26, 40.88 -5.7, 46.05 -11.64 M0 0 C0 0, 0 0, 0 0 M0 0 C0 0, 0 0, 0 0 M12.04 -0.13 C9.55 -2.3, 7.06 -4.46, 1.47 -9.32 M12.04 -0.13 C9.46 -2.38, 6.88 -4.62, 1.47 -9.32 M24.08 -0.27 C16.97 -6.45, 9.86 -12.63, 2.95 -18.64 M24.08 -0.27 C17.96 -5.59, 11.84 -10.91, 2.95 -18.64 M34.61 -1.71 C26.93 -8.39, 19.25 -15.07, 5.93 -26.64 M34.61 -1.71 C23.82 -11.1, 13.02 -20.48, 5.93 -26.64 M43.64 -4.47 C36.36 -10.79, 29.08 -17.12, 11.18 -32.68 M43.64 -4.47 C31.61 -14.92, 19.59 -25.37, 11.18 -32.68 M42.85 -15.76 C35.5 -22.14, 28.15 -28.53, 17.19 -38.06 M42.85 -15.76 C33.23 -24.11, 23.61 -32.47, 17.19 -38.06" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C0.78 -4.11, 1.34 -18.46, 4.68 -24.67 C8.03 -30.87, 14.94 -36.78, 20.07 -37.23 C25.2 -37.68, 31.83 -33.14, 35.45 -27.36 C39.07 -21.58, 47.71 -7.12, 41.81 -2.56 C35.9 2, 6.97 -0.43, 0 0 M0 0 C0.78 -4.11, 1.34 -18.46, 4.68 -24.67 C8.03 -30.87, 14.94 -36.78, 20.07 -37.23 C25.2 -37.68, 31.83 -33.14, 35.45 -27.36 C39.07 -21.58, 47.71 -7.12, 41.81 -2.56 C35.9 2, 6.97 -0.43, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round" transform="translate(41.49670045262869 273.83074989894516) rotate(0 10.702336545928873 9.364544477687804)"><path d="M2.43 3.43 C2.43 3.43, 2.43 3.43, 2.43 3.43 M2.43 3.43 C2.43 3.43, 2.43 3.43, 2.43 3.43 M2.56 15.48 C5.33 12.28, 8.11 9.09, 15.02 1.14 M2.56 15.48 C5.85 11.69, 9.15 7.9, 15.02 1.14 M9.91 19.21 C12.33 16.43, 14.76 13.64, 21.06 6.38 M9.91 19.21 C12.3 16.46, 14.7 13.7, 21.06 6.38 M4.02 16.71 C4.02 16.71, 4.02 16.71, 4.02 16.71 M4.02 16.71 C4.02 16.71, 4.02 16.71, 4.02 16.71 M16.82 17.23 C11.07 12.24, 5.33 7.25, 1.72 4.11 M16.82 17.23 C11.08 12.25, 5.34 7.26, 1.72 4.11 M21.31 10.54 C17.49 7.22, 13.67 3.9, 9.24 0.04 M21.31 10.54 C17.24 7, 13.16 3.46, 9.24 0.04" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M21.4 9.36 C21.4 9.91, 21.35 10.46, 21.24 10.99 C21.13 11.52, 20.97 12.06, 20.76 12.57 C20.55 13.08, 20.28 13.58, 19.97 14.05 C19.66 14.52, 19.3 14.97, 18.9 15.38 C18.5 15.8, 18.06 16.19, 17.58 16.54 C17.11 16.89, 16.59 17.2, 16.05 17.47 C15.52 17.75, 14.94 17.98, 14.36 18.16 C13.78 18.35, 13.17 18.49, 12.56 18.59 C11.95 18.68, 11.32 18.73, 10.7 18.73 C10.08 18.73, 9.45 18.68, 8.84 18.59 C8.23 18.49, 7.62 18.35, 7.04 18.16 C6.46 17.98, 5.89 17.75, 5.35 17.47 C4.81 17.2, 4.3 16.89, 3.82 16.54 C3.35 16.19, 2.9 15.8, 2.5 15.38 C2.11 14.97, 1.74 14.52, 1.43 14.05 C1.12 13.58, 0.86 13.08, 0.65 12.57 C0.43 12.06, 0.27 11.52, 0.16 10.99 C0.06 10.46, 0 9.91, 0 9.36 C0 8.82, 0.06 8.27, 0.16 7.74 C0.27 7.2, 0.43 6.67, 0.65 6.16 C0.86 5.65, 1.12 5.15, 1.43 4.68 C1.74 4.21, 2.11 3.76, 2.5 3.35 C2.9 2.93, 3.35 2.54, 3.82 2.19 C4.3 1.84, 4.81 1.53, 5.35 1.25 C5.89 0.98, 6.46 0.75, 7.04 0.56 C7.62 0.38, 8.23 0.24, 8.84 0.14 C9.45 0.05, 10.08 0, 10.7 0 C11.32 0, 11.95 0.05, 12.56 0.14 C13.17 0.24, 13.78 0.38, 14.36 0.56 C14.94 0.75, 15.52 0.98, 16.05 1.25 C16.59 1.53, 17.11 1.84, 17.58 2.19 C18.06 2.54, 18.5 2.93, 18.9 3.35 C19.3 3.76, 19.66 4.21, 19.97 4.68 C20.28 5.15, 20.55 5.65, 20.76 6.16 C20.97 6.67, 21.13 7.2, 21.24 7.74 C21.35 8.27, 21.38 9.09, 21.4 9.36 C21.43 9.64, 21.43 9.09, 21.4 9.36" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round"><g transform="translate(60.161913756269655 296.73619653372924) rotate(0 16.71865860152218 9.921154001040179)" fill-rule="evenodd"><path d="M0 0 C0 0, 0 0, 0 0 M0 0 C0 0, 0 0, 0 0 M6.04 5.25 C8.63 2.26, 11.23 -0.72, 17.85 -8.34 M6.04 5.25 C9.44 1.34, 12.84 -2.57, 17.85 -8.34 M12.08 10.5 C16.92 4.93, 21.76 -0.64, 25.2 -4.6 M12.08 10.5 C14.86 7.29, 17.65 4.09, 25.2 -4.6 M15.49 18.76 C21.36 12.01, 27.24 5.25, 31.23 0.65 M15.49 18.76 C20.86 12.58, 26.24 6.4, 31.23 0.65 M16.93 29.3 C23.03 22.28, 29.13 15.26, 33.34 10.43 M16.93 29.3 C22.34 23.08, 27.75 16.86, 33.34 10.43 M29.53 27 C31.49 24.74, 33.45 22.49, 34.78 20.96 M29.53 27 C31.57 24.66, 33.6 22.31, 34.78 20.96 M14.43 27.6 C14.43 27.6, 14.43 27.6, 14.43 27.6 M14.43 27.6 C14.43 27.6, 14.43 27.6, 14.43 27.6 M25.72 26.82 C22.82 24.29, 19.92 21.77, 16.66 18.94 M25.72 26.82 C23.31 24.72, 20.91 22.63, 16.66 18.94 M33.98 23.4 C27.09 17.41, 20.2 11.42, 3.04 -3.5 M33.98 23.4 C26.81 17.17, 19.64 10.93, 3.04 -3.5 M36.97 15.4 C28.88 8.37, 20.8 1.34, 9.8 -8.22 M36.97 15.4 C31.4 10.56, 25.83 5.72, 9.8 -8.22" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C0.86 -0.93, 3.58 -4.18, 5.17 -5.57 C6.77 -6.97, 7.56 -7.83, 9.55 -8.36 C11.54 -8.89, 14.99 -8.89, 17.12 -8.76 C19.24 -8.62, 20.83 -8.43, 22.29 -7.56 C23.75 -6.7, 24.88 -5.11, 25.87 -3.58 C26.87 -2.06, 27.47 -0.33, 28.26 1.59 C29.06 3.52, 29.92 5.84, 30.65 7.96 C31.38 10.08, 32.18 12.41, 32.64 14.33 C33.11 16.25, 33.44 17.78, 33.44 19.51 C33.44 21.23, 33.3 23.42, 32.64 24.68 C31.98 25.94, 30.72 26.47, 29.46 27.07 C28.2 27.67, 26.87 28, 25.08 28.26 C23.29 28.53, 20.43 28.73, 18.71 28.66 C16.98 28.59, 15.46 28.93, 14.73 27.86 C14 26.8, 14.66 23.82, 14.33 22.29 C14 20.77, 13.47 20.23, 12.74 18.71 C12.01 17.18, 11.08 15.33, 9.95 13.14 C8.82 10.95, 7.63 7.76, 5.97 5.57 C4.31 3.38, 1 0.93, 0 0 M0 0 C0.86 -0.93, 3.58 -4.18, 5.17 -5.57 C6.77 -6.97, 7.56 -7.83, 9.55 -8.36 C11.54 -8.89, 14.99 -8.89, 17.12 -8.76 C19.24 -8.62, 20.83 -8.43, 22.29 -7.56 C23.75 -6.7, 24.88 -5.11, 25.87 -3.58 C26.87 -2.06, 27.47 -0.33, 28.26 1.59 C29.06 3.52, 29.92 5.84, 30.65 7.96 C31.38 10.08, 32.18 12.41, 32.64 14.33 C33.11 16.25, 33.44 17.78, 33.44 19.51 C33.44 21.23, 33.3 23.42, 32.64 24.68 C31.98 25.94, 30.72 26.47, 29.46 27.07 C28.2 27.67, 26.87 28, 25.08 28.26 C23.29 28.53, 20.43 28.73, 18.71 28.66 C16.98 28.59, 15.46 28.93, 14.73 27.86 C14 26.8, 14.66 23.82, 14.33 22.29 C14 20.77, 13.47 20.23, 12.74 18.71 C12.01 17.18, 11.08 15.33, 9.95 13.14 C8.82 10.95, 7.63 7.76, 5.97 5.57 C4.31 3.38, 1 0.93, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(42.243127302935676 296.7243206303248) rotate(0 -16.121563651467838 12.19394740044196)" fill-rule="evenodd"><path d="M-24.42 -2.68 C-24.42 -2.68, -24.42 -2.68, -24.42 -2.68 M-24.42 -2.68 C-24.42 -2.68, -24.42 -2.68, -24.42 -2.68 M-26.26 11.62 C-20.98 5.55, -15.7 -0.52, -12.48 -4.23 M-26.26 11.62 C-22.34 7.12, -18.43 2.61, -12.48 -4.23 M-29.41 27.44 C-19.17 15.66, -8.93 3.88, -2.51 -3.51 M-29.41 27.44 C-19.18 15.67, -8.95 3.91, -2.51 -3.51 M-22.71 31.93 C-18.15 26.68, -13.58 21.42, -8.28 15.33 M-22.71 31.93 C-17.84 26.33, -12.97 20.73, -8.28 15.33 M-12.74 32.65 C-12.11 31.92, -11.48 31.2, -10.77 30.39 M-12.74 32.65 C-12.17 31.99, -11.6 31.34, -10.77 30.39 M-31.63 25.72 C-31.63 25.72, -31.63 25.72, -31.63 25.72 M-31.63 25.72 C-31.63 25.72, -31.63 25.72, -31.63 25.72 M-13.55 30.83 C-19.05 26.05, -24.55 21.27, -29.4 17.05 M-13.55 30.83 C-19.12 25.99, -24.69 21.15, -29.4 17.05 M-6.79 26.11 C-14.23 19.64, -21.67 13.18, -27.92 7.74 M-6.79 26.11 C-14.66 19.26, -22.53 12.42, -27.92 7.74 M-8.34 14.16 C-12.48 10.56, -16.62 6.97, -24.94 -0.27 M-8.34 14.16 C-12.66 10.41, -16.98 6.65, -24.94 -0.27 M-4.6 6.81 C-8.74 3.22, -12.87 -0.38, -20.45 -6.96 M-4.6 6.81 C-9.74 2.34, -14.89 -2.13, -20.45 -6.96 M-0.1 0.12 C-2.69 -2.13, -5.29 -4.38, -12.93 -11.03 M-0.1 0.12 C-4.04 -3.3, -7.98 -6.72, -12.93 -11.03" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C-0.66 -0.73, -2.59 -3.18, -3.98 -4.38 C-5.37 -5.57, -6.37 -6.63, -8.36 -7.17 C-10.35 -7.7, -13.8 -7.7, -15.92 -7.56 C-18.05 -7.43, -19.64 -7.23, -21.1 -6.37 C-22.56 -5.51, -23.68 -3.91, -24.68 -2.39 C-25.68 -0.86, -26.27 0.86, -27.07 2.79 C-27.86 4.71, -28.73 7.03, -29.46 9.16 C-30.19 11.28, -30.98 13.6, -31.45 15.52 C-31.91 17.45, -32.24 18.97, -32.24 20.7 C-32.24 22.42, -32.11 24.61, -31.45 25.87 C-30.78 27.13, -29.46 27.53, -28.26 28.26 C-27.07 28.99, -26.01 29.72, -24.28 30.25 C-22.56 30.78, -20.1 31.25, -17.91 31.45 C-15.72 31.65, -12.41 32.64, -11.15 31.45 C-9.89 30.25, -10.62 26.07, -10.35 24.28 C-10.08 22.49, -9.89 22.29, -9.55 20.7 C-9.22 19.11, -9.16 17.05, -8.36 14.73 C-7.56 12.41, -6.17 9.22, -4.78 6.77 C-3.38 4.31, -0.8 1.13, 0 0 M0 0 C-0.66 -0.73, -2.59 -3.18, -3.98 -4.38 C-5.37 -5.57, -6.37 -6.63, -8.36 -7.17 C-10.35 -7.7, -13.8 -7.7, -15.92 -7.56 C-18.05 -7.43, -19.64 -7.23, -21.1 -6.37 C-22.56 -5.51, -23.68 -3.91, -24.68 -2.39 C-25.68 -0.86, -26.27 0.86, -27.07 2.79 C-27.86 4.71, -28.73 7.03, -29.46 9.16 C-30.19 11.28, -30.98 13.6, -31.45 15.52 C-31.91 17.45, -32.24 18.97, -32.24 20.7 C-32.24 22.42, -32.11 24.61, -31.45 25.87 C-30.78 27.13, -29.46 27.53, -28.26 28.26 C-27.07 28.99, -26.01 29.72, -24.28 30.25 C-22.56 30.78, -20.1 31.25, -17.91 31.45 C-15.72 31.65, -12.41 32.64, -11.15 31.45 C-9.89 30.25, -10.62 26.07, -10.35 24.28 C-10.08 22.49, -9.89 22.29, -9.55 20.7 C-9.22 19.11, -9.16 17.05, -8.36 14.73 C-7.56 12.41, -6.17 9.22, -4.78 6.77 C-3.38 4.31, -0.8 1.13, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(109.94583739107617 301.79230695929556) rotate(0 69.50582442546883 -0.21775699114179936)"><path d="M0.46 -1.13 C23.33 -1.4, 114.38 -1.34, 137.53 -1.27 M-0.75 0.89 C22.46 0.81, 116.46 0.92, 139.77 0.32" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(109.94583739107617 301.79230695929556) rotate(0 69.50582442546883 -0.21775699114179936)"><path d="M109.8 9.35 C121 8.85, 131.08 2.86, 137.83 -1.25 M111.78 10.88 C117.49 7.38, 126.2 6.02, 140.47 0.9" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(109.94583739107617 301.79230695929556) rotate(0 69.50582442546883 -0.21775699114179936)"><path d="M109.59 -11.17 C120.92 -4.98, 131.06 -4.27, 137.83 -1.25 M111.57 -9.64 C117.47 -8.16, 126.22 -4.54, 140.47 0.9" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(346.6840266018544 299.023439249228) rotate(0 91.89297819086164 -68.33590292315091)"><path d="M0.9 -0.81 C31.56 -23.98, 153.71 -115.18, 183.87 -138.05 M-0.08 1.37 C30.53 -21.76, 152.78 -113.94, 183.51 -137.03" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(346.6840266018544 299.023439249228) rotate(0 91.89297819086164 -68.33590292315091)"><path d="M165.81 -110 C170.08 -120.78, 174.95 -127.54, 181.61 -136.13 M168.12 -110.89 C173.61 -120.46, 178.74 -128.9, 184.02 -137.04" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(346.6840266018544 299.023439249228) rotate(0 91.89297819086164 -68.33590292315091)"><path d="M153.47 -126.39 C161.47 -132.49, 169.93 -134.47, 181.61 -136.13 M155.78 -127.28 C165.69 -131.12, 175.21 -133.74, 184.02 -137.04" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(345.2995927468206 337.7875871901741) rotate(0 97.23161390106503 70.46981831922541)"><path d="M0.56 -1.07 C32.89 22.77, 161.75 117.94, 193.9 142.01" stroke="#000000" stroke-width="1.5" fill="none" stroke-dasharray="8 9"></path></g><g transform="translate(345.2995927468206 337.7875871901741) rotate(0 97.23161390106503 70.46981831922541)"><path d="M163.37 133.57 C172.52 135.21, 183.21 137.65, 194.25 140.82" stroke="#000000" stroke-width="1.5" fill="none"></path></g><g transform="translate(345.2995927468206 337.7875871901741) rotate(0 97.23161390106503 70.46981831922541)"><path d="M175.61 117.09 C181.04 123.62, 188.14 130.88, 194.25 140.82" stroke="#000000" stroke-width="1.5" fill="none"></path></g></g><mask></mask><g transform="translate(344.2668979542183 413.3442172592771) rotate(36.6751652732473 77.04073370879092 7.65143055727205)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="12.24228889163527px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">switch traffic when ready</text></g></svg>
\ No newline at end of file
diff --git a/site/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg b/site/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg
deleted file mode 100644
index f0517c366a..0000000000
--- a/site/assets/img/docs/admin-guide/upgrade/rolling-upgrade.svg
+++ /dev/null
@@ -1,16 +0,0 @@
-<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1035.2128615642703 288.10009003177834" width="2070.4257231285405" height="576.2001800635567">
-  <!-- svg-source:excalidraw -->
-  
-  <defs>
-    <style class="style-fonts">
-      @font-face {
-        font-family: "Virgil";
-        src: url("https://excalidraw.com/Virgil.woff2");
-      }
-      @font-face {
-        font-family: "Cascadia";
-        src: url("https://excalidraw.com/Cascadia.woff2");
-      }
-    </style>
-  </defs>
-  <rect x="0" y="0" width="1035.2128615642703" height="288.10009003177834" fill="#ffffff"></rect><g stroke-linecap="round" transform="translate(572.5859715004883 10) rotate(0 78 23)"><path d="M12.29 1.87 L150.88 2.14 L153.22 1.18 L154.64 8.07 L153.7 39.91 L152.04 44.73 L143.77 45.85 L5.31 44.12 L4.18 42.97 L0.4 38.48 L0.52 9.61 L2.2 3.43 L10.86 -1.47" stroke="none" stroke-width="0" fill="#40c057"></path><path d="M11.5 0 M11.5 0 C55.86 -0.94, 104.69 2.02, 144.5 0 M11.5 0 C52.5 -1.59, 93.8 -0.09, 144.5 0 M144.5 0 C153.34 -1.84, 156.21 3.91, 156 11.5 M144.5 0 C151.21 2.01, 158.25 6.11, 156 11.5 M156 11.5 C156.38 20.39, 157.4 27.42, 156 34.5 M156 11.5 C156.47 16.53, 156.46 23.82, 156 34.5 M156 34.5 C154.88 41.69, 151.57 46.75, 144.5 46 M156 34.5 C153.99 39.99, 151.21 46.01, 144.5 46 M144.5 46 C107.85 47.16, 73.45 44.78, 11.5 46 M144.5 46 C96.28 45.69, 48.24 45.73, 11.5 46 M11.5 46 C2.44 46.17, -0.11 43.81, 0 34.5 M11.5 46 C5.29 45.32, -1.71 40.21, 0 34.5 M0 34.5 C0.18 27.03, 0.55 23.73, 0 11.5 M0 34.5 C0.9 26.51, 0.2 17.09, 0 11.5 M0 11.5 C0.6 2.61, 3.13 -0.22, 11.5 0 M0 11.5 C-0.84 6.1, 2.16 -0.68, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(619.7359730263672 20.5) rotate(0 30.849998474121094 12.5)"><text x="30.849998474121094" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 1</text></g><g stroke-linecap="round" transform="translate(575.3548392105558 84.38443385503382) rotate(0 78 23)"><path d="M11.59 -1.69 L148.35 -0.01 L151.54 3.25 L156.36 9.15 L154.55 39.39 L150.35 43.23 L145.8 45.84 L6.69 46.57 L3.22 43.93 L-0.5 37.75 L-0.46 7.34 L3.82 4.75 L9.99 -1.83" stroke="none" stroke-width="0" fill="#228be6"></path><path d="M11.5 0 M11.5 0 C38.68 1.09, 66.68 -1.3, 144.5 0 M11.5 0 C41.89 -1.91, 71.22 -0.95, 144.5 0 M144.5 0 C151.34 1.75, 157.95 5.81, 156 11.5 M144.5 0 C153.62 -1, 156.37 4.38, 156 11.5 M156 11.5 C155.37 20.22, 155.58 27.19, 156 34.5 M156 11.5 C155.52 15.99, 155.78 21.32, 156 34.5 M156 34.5 C154.25 40.28, 151.33 46.01, 144.5 46 M156 34.5 C155.17 40.86, 153.07 44.2, 144.5 46 M144.5 46 C101.63 46.03, 54.75 45.61, 11.5 46 M144.5 46 C95.7 46.96, 48.24 47.69, 11.5 46 M11.5 46 C5.1 45.41, -1.49 40.47, 0 34.5 M11.5 46 C3.1 47.84, 1.38 42.59, 0 34.5 M0 34.5 C1.16 27.3, 0.05 25.09, 0 11.5 M0 34.5 C0.3 26.21, -0.35 19.03, 0 11.5 M0 11.5 C-0.73 5.8, 2.38 -0.6, 11.5 0 M0 11.5 C-0.4 5.04, 5.33 -2.23, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(618.0948408890226 94.88443385503382) rotate(0 35.2599983215332 12.5)"><text x="35.2599983215332" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 2</text></g><g stroke-linecap="round" transform="translate(577.3548392105558 151.3089630147635) rotate(0 78 23)"><path d="M9.92 0.38 L150.07 1.07 L152.39 2.73 L154.66 7.65 L156.58 39.38 L151.73 45.67 L144.84 46.8 L5.79 45.84 L2.24 41.66 L1.13 39.07 L-1.33 6.98 L0.93 3.68 L12.52 0.21" stroke="none" stroke-width="0" fill="#228be6"></path><path d="M11.5 0 M11.5 0 C61.59 -0.25, 116.2 1.59, 144.5 0 M11.5 0 C38.72 0.83, 67.74 0.94, 144.5 0 M144.5 0 C153.43 -0.87, 156.32 4.31, 156 11.5 M144.5 0 C152.78 1.72, 155.09 2.91, 156 11.5 M156 11.5 C154.04 20.43, 156.68 26.95, 156 34.5 M156 11.5 C155.06 16.91, 155.51 24.21, 156 34.5 M156 34.5 C155.28 41.03, 152.95 44.44, 144.5 46 M156 34.5 C156.74 41.17, 150.17 47.5, 144.5 46 M144.5 46 C97.97 48.39, 50.29 45.11, 11.5 46 M144.5 46 C104.12 46.79, 61.74 46.24, 11.5 46 M11.5 46 C3.2 47.6, 1.2 42.53, 0 34.5 M11.5 46 C2.34 46.84, 1.8 43.59, 0 34.5 M0 34.5 C0.66 29.65, -1.54 25.43, 0 11.5 M0 34.5 C-0.28 30, -0.65 23.22, 0 11.5 M0 11.5 C-0.35 4.88, 5.14 -1.94, 11.5 0 M0 11.5 C0.14 5.14, 1.87 -0.24, 11.5 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(620.4048384476164 161.8089630147635) rotate(0 34.95000076293945 12.5)"><text x="34.95000076293945" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Node 3</text></g><g stroke-linecap="round" transform="translate(169.47649315752938 107.12250893510526) rotate(269.9999999999999 130.8289993006931 40.14858179597991)"><path d="M18.57 -1.83 L239.64 0.8 L251.38 1.47 L258.4 6.27 L260.72 13.85 L260.99 61.7 L261.58 67.16 L254.02 77.55 L240.75 82.05 L22.03 82.28 L12.56 78.17 L3.15 72.93 L0.85 66.43 L-0.48 14.57 L6.22 4.42 L11.95 -0.64 L20.72 0.74" stroke="none" stroke-width="0" fill="#ced4da"></path><path d="M20.07 0 M20.07 0 C74.8 -0.94, 126.59 -0.15, 241.58 0 M20.07 0 C86.95 0.41, 153.42 0.71, 241.58 0 M241.58 0 C253.23 1.31, 262.84 5.29, 261.66 20.07 M241.58 0 C255.85 1.42, 263.82 8.2, 261.66 20.07 M261.66 20.07 C263.33 30.59, 261.1 37.08, 261.66 60.22 M261.66 20.07 C262.13 28.89, 260.88 37.71, 261.66 60.22 M261.66 60.22 C263.23 74.85, 253.17 80.43, 241.58 80.3 M261.66 60.22 C263.26 74.38, 254.95 78.54, 241.58 80.3 M241.58 80.3 C168.3 78.99, 97.1 78.37, 20.07 80.3 M241.58 80.3 C182.29 80.46, 121.92 81.79, 20.07 80.3 M20.07 80.3 C4.99 80.09, 1.26 73.31, 0 60.22 M20.07 80.3 C8.3 82.59, -0.29 74.26, 0 60.22 M0 60.22 C-0.39 44.11, -0.18 29.93, 0 20.07 M0 60.22 C-0.9 47.97, 0.2 34.67, 0 20.07 M0 20.07 C-1.03 8.01, 8.05 -1.11, 20.07 0 M0 20.07 C0.42 7.75, 5.98 0.49, 20.07 0" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(228.71548849093733 134.77109073108517) rotate(269.9999999999999 71.59000396728516 12.5)"><text x="71.59000396728516" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="middle" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Load Balancer</text></g><g transform="translate(23.299615479656723 172.554313963355) rotate(0 28.5 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Users</text></g><g stroke-linecap="round" transform="translate(63.742432418876206 105.29447062901812) rotate(0 9.87517181638475 8.64077533933672)"><path d="M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.98 14.51 C6.68 10.25, 10.39 5.99, 14.13 1.68 M2.98 14.51 C5.69 11.39, 8.4 8.27, 14.13 1.68 M10.33 18.25 C13.95 14.09, 17.57 9.92, 19.51 7.69 M10.33 18.25 C13.82 14.24, 17.31 10.22, 19.51 7.69 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M15.81 15.34 C11.91 11.95, 8.01 8.55, 2.23 3.53 M15.81 15.34 C12.07 12.08, 8.32 8.83, 2.23 3.53 M20.31 8.65 C17.47 6.18, 14.62 3.71, 9.74 -0.54 M20.31 8.65 C16.41 5.25, 12.5 1.86, 9.74 -0.54" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M19.75 8.64 C19.75 9.14, 19.7 9.65, 19.6 10.14 C19.5 10.63, 19.35 11.13, 19.15 11.6 C18.96 12.07, 18.71 12.53, 18.43 12.96 C18.14 13.39, 17.81 13.81, 17.44 14.19 C17.07 14.58, 16.66 14.94, 16.22 15.26 C15.78 15.58, 15.31 15.87, 14.81 16.12 C14.32 16.37, 13.79 16.59, 13.25 16.76 C12.72 16.93, 12.15 17.06, 11.59 17.15 C11.03 17.24, 10.45 17.28, 9.88 17.28 C9.3 17.28, 8.72 17.24, 8.16 17.15 C7.6 17.06, 7.03 16.93, 6.5 16.76 C5.96 16.59, 5.43 16.37, 4.94 16.12 C4.44 15.87, 3.97 15.58, 3.53 15.26 C3.09 14.94, 2.68 14.58, 2.31 14.19 C1.94 13.81, 1.61 13.39, 1.32 12.96 C1.04 12.53, 0.79 12.07, 0.6 11.6 C0.4 11.13, 0.25 10.63, 0.15 10.14 C0.05 9.65, 0 9.14, 0 8.64 C0 8.14, 0.05 7.63, 0.15 7.14 C0.25 6.65, 0.4 6.16, 0.6 5.69 C0.79 5.22, 1.04 4.75, 1.32 4.32 C1.61 3.89, 1.94 3.47, 2.31 3.09 C2.68 2.7, 3.09 2.34, 3.53 2.02 C3.97 1.7, 4.44 1.41, 4.94 1.16 C5.43 0.91, 5.96 0.69, 6.5 0.52 C7.03 0.35, 7.6 0.22, 8.16 0.13 C8.72 0.04, 9.3 0, 9.88 0 C10.45 0, 11.03 0.04, 11.59 0.13 C12.15 0.22, 12.72 0.35, 13.25 0.52 C13.79 0.69, 14.32 0.91, 14.81 1.16 C15.31 1.41, 15.78 1.7, 16.22 2.02 C16.66 2.34, 17.07 2.7, 17.44 3.09 C17.81 3.47, 18.14 3.89, 18.43 4.32 C18.71 4.75, 18.96 5.22, 19.15 5.69 C19.35 6.16, 19.5 6.65, 19.6 7.14 C19.7 7.63, 19.73 8.39, 19.75 8.64 C19.78 8.89, 19.78 8.39, 19.75 8.64" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round" transform="translate(20.55875829455408 105.8775384126522) rotate(0 9.87517181638475 8.64077533933672)"><path d="M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.19 3.23 C2.19 3.23, 2.19 3.23, 2.19 3.23 M2.98 14.51 C5.7 11.38, 8.42 8.25, 14.13 1.68 M2.98 14.51 C5.45 11.67, 7.93 8.82, 14.13 1.68 M10.33 18.25 C12.44 15.82, 14.56 13.39, 19.51 7.69 M10.33 18.25 C13.25 14.89, 16.17 11.53, 19.51 7.69 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M3.77 15.47 C3.77 15.47, 3.77 15.47, 3.77 15.47 M15.81 15.34 C10.62 10.82, 5.42 6.3, 2.23 3.53 M15.81 15.34 C11.57 11.65, 7.33 7.96, 2.23 3.53 M20.31 8.65 C17.85 6.51, 15.39 4.37, 9.74 -0.54 M20.31 8.65 C17.13 5.88, 13.94 3.11, 9.74 -0.54" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M19.75 8.64 C19.75 9.14, 19.7 9.65, 19.6 10.14 C19.5 10.63, 19.35 11.13, 19.15 11.6 C18.96 12.07, 18.71 12.53, 18.43 12.96 C18.14 13.39, 17.81 13.81, 17.44 14.19 C17.07 14.58, 16.66 14.94, 16.22 15.26 C15.78 15.58, 15.31 15.87, 14.81 16.12 C14.32 16.37, 13.79 16.59, 13.25 16.76 C12.72 16.93, 12.15 17.06, 11.59 17.15 C11.03 17.24, 10.45 17.28, 9.88 17.28 C9.3 17.28, 8.72 17.24, 8.16 17.15 C7.6 17.06, 7.03 16.93, 6.5 16.76 C5.96 16.59, 5.43 16.37, 4.94 16.12 C4.44 15.87, 3.97 15.58, 3.53 15.26 C3.09 14.94, 2.68 14.58, 2.31 14.19 C1.94 13.81, 1.61 13.39, 1.32 12.96 C1.04 12.53, 0.79 12.07, 0.6 11.6 C0.4 11.13, 0.25 10.63, 0.15 10.14 C0.05 9.65, 0 9.14, 0 8.64 C0 8.14, 0.05 7.63, 0.15 7.14 C0.25 6.65, 0.4 6.16, 0.6 5.69 C0.79 5.22, 1.04 4.75, 1.32 4.32 C1.61 3.89, 1.94 3.47, 2.31 3.09 C2.68 2.7, 3.09 2.34, 3.53 2.02 C3.97 1.7, 4.44 1.41, 4.94 1.16 C5.43 0.91, 5.96 0.69, 6.5 0.52 C7.03 0.35, 7.6 0.22, 8.16 0.13 C8.72 0.04, 9.3 0, 9.88 0 C10.45 0, 11.03 0.04, 11.59 0.13 C12.15 0.22, 12.72 0.35, 13.25 0.52 C13.79 0.69, 14.32 0.91, 14.81 1.16 C15.31 1.41, 15.78 1.7, 16.22 2.02 C16.66 2.34, 17.07 2.7, 17.44 3.09 C17.81 3.47, 18.14 3.89, 18.43 4.32 C18.71 4.75, 18.96 5.22, 19.15 5.69 C19.35 6.16, 19.5 6.65, 19.6 7.14 C19.7 7.63, 19.73 8.39, 19.75 8.64 C19.78 8.89, 19.78 8.39, 19.75 8.64" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round"><g transform="translate(31.01057830181867 164.8085741503018) rotate(0 21.90843989373377 -18.494048425191174)" fill-rule="evenodd"><path d="M11.93 -33.36 C11.93 -33.36, 11.93 -33.36, 11.93 -33.36 M11.93 -33.36 C11.93 -33.36, 11.93 -33.36, 11.93 -33.36 M6.81 -15.28 C10.73 -19.78, 14.64 -24.29, 25.18 -36.41 M6.81 -15.28 C13.83 -23.35, 20.84 -31.42, 25.18 -36.41 M2.35 2.04 C13.52 -10.81, 24.69 -23.66, 31.87 -31.92 M2.35 2.04 C10.88 -7.77, 19.41 -17.58, 31.87 -31.92 M12.98 2.01 C18.19 -3.99, 23.41 -9.99, 37.25 -25.92 M12.98 2.01 C20.13 -6.21, 27.28 -14.44, 37.25 -25.92 M23.61 1.97 C28.01 -3.09, 32.42 -8.16, 41.32 -18.4 M23.61 1.97 C30.52 -5.98, 37.44 -13.93, 41.32 -18.4 M34.9 1.19 C38.82 -3.33, 42.75 -7.85, 46.05 -11.64 M34.9 1.19 C39.31 -3.89, 43.73 -8.97, 46.05 -11.64 M0 0 C0 0, 0 0, 0 0 M0 0 C0 0, 0 0, 0 0 M12.04 -0.13 C8.29 -3.39, 4.55 -6.65, 1.47 -9.32 M12.04 -0.13 C9.05 -2.73, 6.06 -5.33, 1.47 -9.32 M24.08 -0.27 C19.22 -4.49, 14.36 -8.72, 2.95 -18.64 M24.08 -0.27 C15.87 -7.4, 7.67 -14.54, 2.95 -18.64 M34.61 -1.71 C23.59 -11.29, 12.57 -20.87, 5.93 -26.64 M34.61 -1.71 C26.15 -9.06, 17.7 -16.42, 5.93 -26.64 M43.64 -4.47 C34.21 -12.66, 24.79 -20.85, 11.18 -32.68 M43.64 -4.47 C32.66 -14.01, 21.68 -23.55, 11.18 -32.68 M42.85 -15.76 C34.22 -23.25, 25.6 -30.75, 17.19 -38.06 M42.85 -15.76 C37.38 -20.5, 31.92 -25.25, 17.19 -38.06" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C0.78 -4.11, 1.34 -18.46, 4.68 -24.67 C8.03 -30.87, 14.94 -36.78, 20.07 -37.23 C25.2 -37.68, 31.83 -33.14, 35.45 -27.36 C39.07 -21.58, 47.71 -7.12, 41.81 -2.56 C35.9 2, 6.97 -0.43, 0 0 M0 0 C0.78 -4.11, 1.34 -18.46, 4.68 -24.67 C8.03 -30.87, 14.94 -36.78, 20.07 -37.23 C25.2 -37.68, 31.83 -33.14, 35.45 -27.36 C39.07 -21.58, 47.71 -7.12, 41.81 -2.56 C35.9 2, 6.97 -0.43, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round" transform="translate(41.4967004526286 108.23406283046478) rotate(0 10.702336545928915 9.364544477687808)"><path d="M2.43 3.43 C2.43 3.43, 2.43 3.43, 2.43 3.43 M2.43 3.43 C2.43 3.43, 2.43 3.43, 2.43 3.43 M2.56 15.48 C5.21 12.43, 7.86 9.38, 15.02 1.14 M2.56 15.48 C7.11 10.24, 11.67 5, 15.02 1.14 M9.91 19.21 C13.96 14.55, 18.01 9.9, 21.06 6.38 M9.91 19.21 C13.95 14.57, 17.98 9.93, 21.06 6.38 M4.02 16.71 C4.02 16.71, 4.02 16.71, 4.02 16.71 M4.02 16.71 C4.02 16.71, 4.02 16.71, 4.02 16.71 M16.82 17.23 C12.86 13.79, 8.9 10.35, 1.72 4.11 M16.82 17.23 C11.29 12.43, 5.77 7.63, 1.72 4.11 M21.31 10.54 C17.9 7.58, 14.49 4.61, 9.24 0.04 M21.31 10.54 C16.98 6.77, 12.64 3.01, 9.24 0.04" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M21.4 9.36 C21.4 9.91, 21.35 10.46, 21.24 10.99 C21.13 11.52, 20.97 12.06, 20.76 12.57 C20.55 13.08, 20.28 13.58, 19.97 14.05 C19.66 14.52, 19.3 14.97, 18.9 15.38 C18.5 15.8, 18.06 16.19, 17.58 16.54 C17.11 16.89, 16.59 17.2, 16.05 17.47 C15.52 17.75, 14.94 17.98, 14.36 18.16 C13.78 18.35, 13.17 18.49, 12.56 18.59 C11.95 18.68, 11.32 18.73, 10.7 18.73 C10.08 18.73, 9.45 18.68, 8.84 18.59 C8.23 18.49, 7.62 18.35, 7.04 18.16 C6.46 17.98, 5.89 17.75, 5.35 17.47 C4.81 17.2, 4.3 16.89, 3.82 16.54 C3.35 16.19, 2.9 15.8, 2.5 15.38 C2.11 14.97, 1.74 14.52, 1.43 14.05 C1.12 13.58, 0.86 13.08, 0.65 12.57 C0.43 12.06, 0.27 11.52, 0.16 10.99 C0.06 10.46, 0 9.91, 0 9.36 C0 8.82, 0.06 8.27, 0.16 7.74 C0.27 7.2, 0.43 6.67, 0.65 6.16 C0.86 5.65, 1.12 5.15, 1.43 4.68 C1.74 4.21, 2.11 3.76, 2.5 3.35 C2.9 2.93, 3.35 2.54, 3.82 2.19 C4.3 1.84, 4.81 1.53, 5.35 1.25 C5.89 0.98, 6.46 0.75, 7.04 0.56 C7.62 0.38, 8.23 0.24, 8.84 0.14 C9.45 0.05, 10.08 0, 10.7 0 C11.32 0, 11.95 0.05, 12.56 0.14 C13.17 0.24, 13.78 0.38, 14.36 0.56 C14.94 0.75, 15.52 0.98, 16.05 1.25 C16.59 1.53, 17.11 1.84, 17.58 2.19 C18.06 2.54, 18.5 2.93, 18.9 3.35 C19.3 3.76, 19.66 4.21, 19.97 4.68 C20.28 5.15, 20.55 5.65, 20.76 6.16 C20.97 6.67, 21.13 7.2, 21.24 7.74 C21.35 8.27, 21.38 9.09, 21.4 9.36 C21.43 9.64, 21.43 9.09, 21.4 9.36" stroke="#000000" stroke-width="2" fill="none"></path></g><g stroke-linecap="round"><g transform="translate(60.16191375626954 131.13950946524886) rotate(0 16.71865860152218 9.921154001040179)" fill-rule="evenodd"><path d="M0 0 C0 0, 0 0, 0 0 M0 0 C0 0, 0 0, 0 0 M6.04 5.25 C9.16 1.65, 12.29 -1.95, 17.85 -8.34 M6.04 5.25 C10.25 0.4, 14.46 -4.44, 17.85 -8.34 M12.08 10.5 C15.01 7.13, 17.94 3.75, 25.2 -4.6 M12.08 10.5 C14.97 7.17, 17.86 3.84, 25.2 -4.6 M15.49 18.76 C19.46 14.19, 23.44 9.62, 31.23 0.65 M15.49 18.76 C19.67 13.96, 23.85 9.15, 31.23 0.65 M16.93 29.3 C21.06 24.55, 25.19 19.8, 33.34 10.43 M16.93 29.3 C20.79 24.86, 24.64 20.43, 33.34 10.43 M29.53 27 C30.67 25.69, 31.81 24.38, 34.78 20.96 M29.53 27 C31.37 24.88, 33.21 22.77, 34.78 20.96 M14.43 27.6 C14.43 27.6, 14.43 27.6, 14.43 27.6 M14.43 27.6 C14.43 27.6, 14.43 27.6, 14.43 27.6 M25.72 26.82 C23.22 24.65, 20.73 22.48, 16.66 18.94 M25.72 26.82 C23.72 25.08, 21.73 23.35, 16.66 18.94 M33.98 23.4 C23.4 14.21, 12.83 5.01, 3.04 -3.5 M33.98 23.4 C26.2 16.64, 18.42 9.87, 3.04 -3.5 M36.97 15.4 C26.72 6.49, 16.47 -2.42, 9.8 -8.22 M36.97 15.4 C30.82 10.05, 24.67 4.71, 9.8 -8.22" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C0.86 -0.93, 3.58 -4.18, 5.17 -5.57 C6.77 -6.97, 7.56 -7.83, 9.55 -8.36 C11.54 -8.89, 14.99 -8.89, 17.12 -8.76 C19.24 -8.62, 20.83 -8.43, 22.29 -7.56 C23.75 -6.7, 24.88 -5.11, 25.87 -3.58 C26.87 -2.06, 27.47 -0.33, 28.26 1.59 C29.06 3.52, 29.92 5.84, 30.65 7.96 C31.38 10.08, 32.18 12.41, 32.64 14.33 C33.11 16.25, 33.44 17.78, 33.44 19.51 C33.44 21.23, 33.3 23.42, 32.64 24.68 C31.98 25.94, 30.72 26.47, 29.46 27.07 C28.2 27.67, 26.87 28, 25.08 28.26 C23.29 28.53, 20.43 28.73, 18.71 28.66 C16.98 28.59, 15.46 28.93, 14.73 27.86 C14 26.8, 14.66 23.82, 14.33 22.29 C14 20.77, 13.47 20.23, 12.74 18.71 C12.01 17.18, 11.08 15.33, 9.95 13.14 C8.82 10.95, 7.63 7.76, 5.97 5.57 C4.31 3.38, 1 0.93, 0 0 M0 0 C0.86 -0.93, 3.58 -4.18, 5.17 -5.57 C6.77 -6.97, 7.56 -7.83, 9.55 -8.36 C11.54 -8.89, 14.99 -8.89, 17.12 -8.76 C19.24 -8.62, 20.83 -8.43, 22.29 -7.56 C23.75 -6.7, 24.88 -5.11, 25.87 -3.58 C26.87 -2.06, 27.47 -0.33, 28.26 1.59 C29.06 3.52, 29.92 5.84, 30.65 7.96 C31.38 10.08, 32.18 12.41, 32.64 14.33 C33.11 16.25, 33.44 17.78, 33.44 19.51 C33.44 21.23, 33.3 23.42, 32.64 24.68 C31.98 25.94, 30.72 26.47, 29.46 27.07 C28.2 27.67, 26.87 28, 25.08 28.26 C23.29 28.53, 20.43 28.73, 18.71 28.66 C16.98 28.59, 15.46 28.93, 14.73 27.86 C14 26.8, 14.66 23.82, 14.33 22.29 C14 20.77, 13.47 20.23, 12.74 18.71 C12.01 17.18, 11.08 15.33, 9.95 13.14 C8.82 10.95, 7.63 7.76, 5.97 5.57 C4.31 3.38, 1 0.93, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(42.24312730293559 131.12763356184445) rotate(0 -16.121563651467795 12.193947400441964)" fill-rule="evenodd"><path d="M-24.42 -2.68 C-24.42 -2.68, -24.42 -2.68, -24.42 -2.68 M-24.42 -2.68 C-24.42 -2.68, -24.42 -2.68, -24.42 -2.68 M-26.26 11.62 C-22.63 7.45, -19 3.27, -12.48 -4.23 M-26.26 11.62 C-22.27 7.03, -18.28 2.44, -12.48 -4.23 M-29.41 27.44 C-22.35 19.32, -15.29 11.2, -2.51 -3.51 M-29.41 27.44 C-19.56 16.11, -9.71 4.78, -2.51 -3.51 M-22.71 31.93 C-18.64 27.24, -14.56 22.56, -8.28 15.33 M-22.71 31.93 C-17.53 25.97, -12.35 20.01, -8.28 15.33 M-12.74 32.65 C-12.15 31.98, -11.57 31.3, -10.77 30.39 M-12.74 32.65 C-12.23 32.07, -11.73 31.49, -10.77 30.39 M-31.63 25.72 C-31.63 25.72, -31.63 25.72, -31.63 25.72 M-31.63 25.72 C-31.63 25.72, -31.63 25.72, -31.63 25.72 M-13.55 30.83 C-17.43 27.46, -21.3 24.09, -29.4 17.05 M-13.55 30.83 C-19.26 25.87, -24.96 20.91, -29.4 17.05 M-6.79 26.11 C-12.88 20.81, -18.98 15.52, -27.92 7.74 M-6.79 26.11 C-13.07 20.65, -19.34 15.2, -27.92 7.74 M-8.34 14.16 C-11.82 11.14, -15.3 8.11, -24.94 -0.27 M-8.34 14.16 C-12.4 10.63, -16.47 7.09, -24.94 -0.27 M-4.6 6.81 C-9.6 2.47, -14.6 -1.88, -20.45 -6.96 M-4.6 6.81 C-9 2.98, -13.41 -0.85, -20.45 -6.96 M-0.1 0.12 C-4.38 -3.6, -8.66 -7.32, -12.93 -11.03 M-0.1 0.12 C-2.96 -2.36, -5.81 -4.84, -12.93 -11.03" stroke="#ced4da" stroke-width="1" fill="none"></path><path d="M0 0 C-0.66 -0.73, -2.59 -3.18, -3.98 -4.38 C-5.37 -5.57, -6.37 -6.63, -8.36 -7.17 C-10.35 -7.7, -13.8 -7.7, -15.92 -7.56 C-18.05 -7.43, -19.64 -7.23, -21.1 -6.37 C-22.56 -5.51, -23.68 -3.91, -24.68 -2.39 C-25.68 -0.86, -26.27 0.86, -27.07 2.79 C-27.86 4.71, -28.73 7.03, -29.46 9.16 C-30.19 11.28, -30.98 13.6, -31.45 15.52 C-31.91 17.45, -32.24 18.97, -32.24 20.7 C-32.24 22.42, -32.11 24.61, -31.45 25.87 C-30.78 27.13, -29.46 27.53, -28.26 28.26 C-27.07 28.99, -26.01 29.72, -24.28 30.25 C-22.56 30.78, -20.1 31.25, -17.91 31.45 C-15.72 31.65, -12.41 32.64, -11.15 31.45 C-9.89 30.25, -10.62 26.07, -10.35 24.28 C-10.08 22.49, -9.89 22.29, -9.55 20.7 C-9.22 19.11, -9.16 17.05, -8.36 14.73 C-7.56 12.41, -6.17 9.22, -4.78 6.77 C-3.38 4.31, -0.8 1.13, 0 0 M0 0 C-0.66 -0.73, -2.59 -3.18, -3.98 -4.38 C-5.37 -5.57, -6.37 -6.63, -8.36 -7.17 C-10.35 -7.7, -13.8 -7.7, -15.92 -7.56 C-18.05 -7.43, -19.64 -7.23, -21.1 -6.37 C-22.56 -5.51, -23.68 -3.91, -24.68 -2.39 C-25.68 -0.86, -26.27 0.86, -27.07 2.79 C-27.86 4.71, -28.73 7.03, -29.46 9.16 C-30.19 11.28, -30.98 13.6, -31.45 15.52 C-31.91 17.45, -32.24 18.97, -32.24 20.7 C-32.24 22.42, -32.11 24.61, -31.45 25.87 C-30.78 27.13, -29.46 27.53, -28.26 28.26 C-27.07 28.99, -26.01 29.72, -24.28 30.25 C-22.56 30.78, -20.1 31.25, -17.91 31.45 C-15.72 31.65, -12.41 32.64, -11.15 31.45 C-9.89 30.25, -10.62 26.07, -10.35 24.28 C-10.08 22.49, -9.89 22.29, -9.55 20.7 C-9.22 19.11, -9.16 17.05, -8.36 14.73 C-7.56 12.41, -6.17 9.22, -4.78 6.77 C-3.38 4.31, -0.8 1.13, 0 0" stroke="#000000" stroke-width="2" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(109.94583739107611 136.19561989081518) rotate(0 69.86077098192868 -0.628256155844543)"><path d="M0.76 -0.52 C23.9 -0.9, 116.79 -1.11, 140.02 -1.1 M-0.3 1.82 C22.6 1.56, 115.87 -2.38, 139.18 -3.07" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(109.94583739107611 136.19561989081518) rotate(0 69.86077098192868 -0.628256155844543)"><path d="M110.51 8.53 C122.8 4.08, 134.88 -1.74, 138.37 -1.87 M111.7 8.58 C118.29 5.18, 126.07 2.75, 138.3 -4.02" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(109.94583739107611 136.19561989081518) rotate(0 69.86077098192868 -0.628256155844543)"><path d="M109.76 -11.98 C122.55 -8.28, 134.93 -5.94, 138.37 -1.87 M110.95 -11.93 C117.82 -9.77, 125.79 -6.67, 138.3 -4.02" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(349.4528943119219 141.58654175254128) rotate(0 97.18164883703821 -0.7118767047838226)"><path d="M0.19 0.29 C32.65 0.36, 163.1 0.21, 195.53 -0.08 M-1.16 -0.61 C31.1 -0.82, 162.27 -1.76, 194.75 -1.73" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(349.4528943119219 141.58654175254128) rotate(0 97.18164883703821 -0.7118767047838226)"><path d="M167.07 9.17 C178.37 4.03, 186.29 2.26, 194.15 -1.07 M166.04 8.4 C172.04 6.78, 177.25 3.33, 194.33 -1.72" stroke="#000000" stroke-width="1" fill="none"></path></g><g transform="translate(349.4528943119219 141.58654175254128) rotate(0 97.18164883703821 -0.7118767047838226)"><path d="M167 -11.35 C178.23 -9.03, 186.18 -3.35, 194.15 -1.07 M165.96 -12.12 C172.05 -9.53, 177.27 -8.76, 194.33 -1.72" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(352.2217620219892 90.64891427363261) rotate(0 94.69918799397601 -23.79390688422322)"><path d="M0.72 -0.36 C32.25 -8.15, 157.35 -39.68, 188.68 -47.23" stroke="#000000" stroke-width="1.5" fill="none" stroke-dasharray="8 9"></path></g><g transform="translate(352.2217620219892 90.64891427363261) rotate(0 94.69918799397601 -23.79390688422322)"><path d="M163.18 -29.85 C168.43 -34.36, 177.55 -40.48, 188.2 -47.83" stroke="#000000" stroke-width="1.5" fill="none"></path></g><g transform="translate(352.2217620219892 90.64891427363261) rotate(0 94.69918799397601 -23.79390688422322)"><path d="M158.25 -49.77 C164.71 -49.13, 175.11 -50.06, 188.2 -47.83" stroke="#000000" stroke-width="1.5" fill="none"></path></g></g><mask></mask><g transform="translate(355.64421201976756 33.634031146009704) rotate(344.9033703822942 75.51600646972656 7.65143055727205)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="12.24228889163527px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">switch traffic when ready</text></g><g stroke-linecap="round"><g transform="translate(550.227658707631 76.9681642912675) rotate(0 0.4614221589972658 70.95185539230519)"><path d="M-0.16 0.1 C-0.25 23.51, 0.02 117.7, 0.42 141.24 M-1.7 -0.89 C-1.5 22.65, 2.01 118.85, 2.62 142.8" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(548.8432248525971 76.9681642912675) rotate(0 23.259719931793143 -0.9142844041955271)"><path d="M-0.32 0.45 C7.51 0.25, 38.94 -0.42, 46.84 -0.58 M1.72 -0.35 C9.37 -0.95, 38.34 -1.94, 45.76 -2.28" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g stroke-linecap="round"><g transform="translate(548.8432248525971 218.18041750471411) rotate(0 31.250096698352195 -1.775462741694696)"><path d="M1.08 -0.37 C11.33 -1.06, 52.29 -2.87, 62.31 -3.18 M0.19 -1.61 C10.2 -2.21, 50.82 -1.41, 61.37 -1.86" stroke="#000000" stroke-width="1" fill="none"></path></g></g><mask></mask><g transform="translate(745.4328322673953 17.43750852481452) rotate(0 139.8900146484375 12.5)"><text x="0" y="0" font-family="Virgil, Segoe UI Emoji" font-size="20px" fill="#000000" text-anchor="start" style="white-space: pre;" direction="ltr" dominant-baseline="text-before-edge">Upgrade one node at a time</text></g></svg>
\ No newline at end of file
diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 4426a13117..124549afc6 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -4,6 +4,7 @@ title: Upgrade FusionAuth
 description: Learn how to upgrade FusionAuth using our bundles and migration scripts
 navcategory: admin
 ---
+:page-liquid:
 
 == Upgrading
 
@@ -12,8 +13,8 @@ If you're considering upgrading FusionAuth to a later version, this document wil
 Topics covered in this document:
 
 * <<When to Upgrade>>
-** <<Reasons to Upgrade>>
-** <<Reasons not to Upgrade>>
+** <<Reasons To Upgrade>>
+** <<Reasons Not To Upgrade>>
 ** <<Being Aware of Upgrade Options>>
 * <<How to Think About Upgrades>>
 ** <<Update Contents and Notes>>
@@ -144,7 +145,9 @@ A rolling upgrade procedure might look like this:
 
 There is still some downtime with this procedure, but it is limited to the time it takes to run the database migration on the upgraded first node. There will be limited capacity during the upgrade, especially while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
 
-image::admin-guide/upgrade/blue-green.svg[A representation of a Rolling upgrade.,width=600]
+++++
+{% plantuml source: _diagrams/docs/admin-guide/rolling_upgrade.plantuml, alt: "Rolling upgrade." %}
+++++
 
 === Blue-Green Deployment
 
@@ -152,7 +155,9 @@ A blue-green deployment is a technique that reduces downtime and risk by running
 
 To perform a blue-green deployment with a three-node cluster, first create three new nodes. Add one of these nodes to the existing cluster. At this point, the new node will lock the database and own it while it completes the database upgrade. The original nodes might give errors, as they will not have access to the database. They can be removed. The remaining new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
 
-image::admin-guide/upgrade/rolling-upgrade.svg[A representation of a Blue/Green upgrade.,width=600]
+++++
+{% plantuml source: _diagrams/docs/admin-guide/blue_green_upgrade.plantuml, alt: "Blue green deployment." %}
+++++
  
 === Out-of-Band Database Upgrades
 
@@ -252,20 +257,20 @@ A: We publish release notes for every release. You can find them here: link:/doc
 
 This section will guide you with detailed technical instructions on how to upgrade FusionAuth nodes on different platforms.
 
-[NOTE]
-====
-*Readme*
 
-To upgrade to the latest version of FusionAuth using the FastPath installation, go link:/docs/v1/tech/installation-guide/fast-path[here].
+=== Docker
+
+include::docs/v1/tech/shared/_upgrade-using-docker.adoc[]
 
-To upgrade to the latest version of FusionAuth using Homebrew, go link:/docs/v1/tech/installation-guide/homebrew[here].
+=== Homebrew
 
-To upgrade to the latest version of FusionAuth using Docker, go link:/docs/v1/tech/installation-guide/docker[here].
+include::docs/v1/tech/shared/_upgrade-using-brew.adoc[]
 
+[NOTE]
+====
 If you want to use manual mode, download the latest version of FusionAuth and follow the instructions below. See https://fusionauth.io/download[Downloads].
 ====
 
-
 === ZIP Packages
 
 FusionAuth is available in a ZIP package for macOS, Linux, and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth.
diff --git a/site/docs/v1/tech/installation-guide/docker.adoc b/site/docs/v1/tech/installation-guide/docker.adoc
index 08aa2f02d5..44abbcaf69 100644
--- a/site/docs/v1/tech/installation-guide/docker.adoc
+++ b/site/docs/v1/tech/installation-guide/docker.adoc
@@ -199,12 +199,7 @@ image:installation-guides/mailcatcher-client.png[Mailcatcher Client View,width=1
 
 == Upgrading
 
-To upgrade FusionAuth when running with `docker-compose`:
-
-. Stop the instance: `docker-compose down`.
-. Modify the `docker-compose.yml` file to point to the version of FusionAuth you want. You can see https://hub.docker.com/r/fusionauth/fusionauth-app[available tags].
-. Start it up: `docker-compose up`.
-. Login to the administrative UI. 
+include::docs/v1/tech/shared/_upgrade-using-docker.adoc[]
 
 === Migrations
 
diff --git a/site/docs/v1/tech/installation-guide/homebrew.adoc b/site/docs/v1/tech/installation-guide/homebrew.adoc
index 658ec2a964..77e6cb0ca8 100644
--- a/site/docs/v1/tech/installation-guide/homebrew.adoc
+++ b/site/docs/v1/tech/installation-guide/homebrew.adoc
@@ -38,28 +38,4 @@ The shared configuration file will be located here: `/usr/local/etc/fusionauth/f
 
 == Homebrew Upgrade
 
-If you initially installed FusionAuth using Homebrew, you can also use Homebrew to upgrade to the latest version of FusionAuth.
-
-To upgrade FusionAuth using brew, first stop services.
-
-```
-brew services stop fusionauth-search
-brew services stop fusionauth-app
-```
-
-Next, upgrade services.
-
-:code_id: homebrew-upgrade-script
-[source]
-----
-brew upgrade fusionauth-app fusionauth-search
-----
-:code_id!:
-
-Start the services.
-
-[source]
-----
-brew services start fusionauth-search
-brew services start fusionauth-app
-----
+include::docs/v1/tech/shared/_upgrade-using-brew.adoc[]
diff --git a/site/docs/v1/tech/shared/_upgrade-using-brew.adoc b/site/docs/v1/tech/shared/_upgrade-using-brew.adoc
new file mode 100644
index 0000000000..8e1cc744f4
--- /dev/null
+++ b/site/docs/v1/tech/shared/_upgrade-using-brew.adoc
@@ -0,0 +1,25 @@
+If you initially installed FusionAuth using Homebrew, you can also use Homebrew to upgrade to the latest version of FusionAuth.
+
+To upgrade FusionAuth using brew, first stop services.
+
+```
+brew services stop fusionauth-search
+brew services stop fusionauth-app
+```
+
+Next, upgrade services.
+
+:code_id: homebrew-upgrade-script
+[source]
+----
+brew upgrade fusionauth-app fusionauth-search
+----
+:code_id!:
+
+Start the services.
+
+[source]
+----
+brew services start fusionauth-search
+brew services start fusionauth-app
+----
\ No newline at end of file
diff --git a/site/docs/v1/tech/shared/_upgrade-using-docker.adoc b/site/docs/v1/tech/shared/_upgrade-using-docker.adoc
new file mode 100644
index 0000000000..04bcec9663
--- /dev/null
+++ b/site/docs/v1/tech/shared/_upgrade-using-docker.adoc
@@ -0,0 +1,6 @@
+To upgrade FusionAuth when running with `docker-compose`:
+
+. Stop the instance: `docker-compose down`.
+. Modify the `docker-compose.yml` file to point to the version of FusionAuth you want. You can see https://hub.docker.com/r/fusionauth/fusionauth-app[available tags].
+. Start it up: `docker-compose up`.
+. Login to the administrative UI.
\ No newline at end of file

From c13a834d31dc73f678eb89bcc8e71bf692545d84 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Wed, 21 Jun 2023 00:31:24 +0200
Subject: [PATCH 23/55] -theme upgrade additions

---
 .../installation-guide/_theme-upgrade.adoc    | 32 +++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
index 0271343ce2..e16129dd16 100644
--- a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
+++ b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
@@ -8,6 +8,38 @@ As part of your upgrade testing, open the administrative user interface and navi
 
 If any themes are missing templates, they will show as "Upgrade Required". Port the new theme files over to your custom theme, modify them as needed, and save the theme.
 
+In some cases, existing templates are modified. If you have customized your theme, you'll need to compare the new template to your existing versions base theme, and port over any changes to your customized theme. The easiest way to do this is to use a diff tool to compare the two sets of files. Here is a suggested process, before you upgrade:
+
+1. Download the default theme from your existing version of FusionAuth.
+2. Download the default theme from the new version of FusionAuth.
+3. Use a diff tool to compare the two sets of files. 
+4. Apply any differences to your customized theme.
+
+You can use the https://github.com/FusionAuth/fusionauth-theme-helper[Them Helper] to help  with this process.
+
+==== Using the Theme Helper to Upgrade Themes
+
+Clone the https://github.com/FusionAuth/fusionauth-theme-helper[Them Helper] repo and follow the install instructions in the `README.md` file. Now, you'll need to download the base themes from your existing version of FusionAuth and the new version of FusionAuth to compare. 
+
+To get the existing version's theme files, create a `.env` file from the `.env.sample` file. Create an https://fusionauth.io/docs/v1/tech/apis/authentication#managing-api-keys[API key] with read permissions for Themes in the FusionAuth administrative user interface. Add the API key to the `.env` file. Navigate to [breadcrumb]#Customizations -> Themes# and copy the ID of the default "FusionAuth" theme. Use this value to update the `THEME_ID` key in the .env file. 
+
+In the `.env` file, set the `FUSIONAUTH_URL` to the URL of your existing FusionAuth instance. Finally, update the `TMP_DIR` to a directory on your local machine where you want the existing theme files to be downloaded, such as `current-theme`.
+
+Now you can run the `download.sh` script to download the existing theme files to the `TMP_DIR` directory.
+
+Once this has completed downloading, you'll need to get the base theme files from the new version of FusionAuth. The easiest way to do this before upgrading your production version is to install the new version of FusionAuth on your local machine or a VM using Docker. Instructions for installing FusionAuth using Docker can be found in the https://fusionauth.io/docs/v1/tech/installation-guide/docker#docker-compose[FusionAuth Docker Installation Guide].
+
+Once you've got the new version of FusionAuth running, you can update the Theme Helper `.env` file in the Theme Helper repo to point to the new version of FusionAuth. You'll need to update the `FUSIONAUTH_URL` to `http://localhost:9011`. You'll also need to login to the new FusionAuth to create an API key, and copy the default theme ID into `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
+
+Now you can run the `download.sh` script again to download the new theme files to the `TMP_DIR` directory.
+
+Once you have both sets of theme files downloaded, you can run the `diff-themes.sh` script to compare the two sets of files. The script takes 2 arguments, the first is the path to the existing theme files, and the second is the path to the new theme files. For example:
+
+```sh
+./diff-themes.sh current-theme new-theme
+```
+The script will output a list of files that are different between the two sets of theme files, along with the differences. You can use this list to update your customized theme files. While you can directly use this output to find the changes, it might be useful to use a visual diff tool of your choice to help you make the changes, using the file list as a guide.
+
 === Messages
 
 When new functionality is introduced to link:/docs/v1/tech/core-concepts/integration-points#hosted-login-pages[the hosted login pages], new theme message keys are sometimes required. They are added to the default theme `messages` file by the upgrade process. 

From ccca5bba55b83851dd3e9ff7d9ef2d869ccd3675 Mon Sep 17 00:00:00 2001
From: Tatenda <31291528+rideam@users.noreply.github.com>
Date: Wed, 21 Jun 2023 16:43:07 +0200
Subject: [PATCH 24/55] text updates

---
 .../v1/tech/installation-guide/_theme-upgrade.adoc     | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
index e16129dd16..f6b3cda70e 100644
--- a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
+++ b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
@@ -15,21 +15,21 @@ In some cases, existing templates are modified. If you have customized your them
 3. Use a diff tool to compare the two sets of files. 
 4. Apply any differences to your customized theme.
 
-You can use the https://github.com/FusionAuth/fusionauth-theme-helper[Them Helper] to help  with this process.
+You can use the link:https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] to help  with this process.
 
 ==== Using the Theme Helper to Upgrade Themes
 
-Clone the https://github.com/FusionAuth/fusionauth-theme-helper[Them Helper] repo and follow the install instructions in the `README.md` file. Now, you'll need to download the base themes from your existing version of FusionAuth and the new version of FusionAuth to compare. 
+Clone the link:https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] repo and follow the install instructions in the `README.md` file. Now, you'll need to download the base themes from your existing version of FusionAuth and the new version of FusionAuth to compare.
 
-To get the existing version's theme files, create a `.env` file from the `.env.sample` file. Create an https://fusionauth.io/docs/v1/tech/apis/authentication#managing-api-keys[API key] with read permissions for Themes in the FusionAuth administrative user interface. Add the API key to the `.env` file. Navigate to [breadcrumb]#Customizations -> Themes# and copy the ID of the default "FusionAuth" theme. Use this value to update the `THEME_ID` key in the .env file. 
+To get the existing version's theme files, create a `.env` file from the `.env.sample` file. Create an link:/docs/v1/tech/apis/authentication#managing-api-keys[API key] with read permissions for Themes in the FusionAuth administrative user interface. Add the API key to the `.env` file. Navigate to [breadcrumb]#Customizations -> Themes# and copy the ID of the default "FusionAuth" theme. Use this value to update the `THEME_ID` key in the .env file.
 
 In the `.env` file, set the `FUSIONAUTH_URL` to the URL of your existing FusionAuth instance. Finally, update the `TMP_DIR` to a directory on your local machine where you want the existing theme files to be downloaded, such as `current-theme`.
 
 Now you can run the `download.sh` script to download the existing theme files to the `TMP_DIR` directory.
 
-Once this has completed downloading, you'll need to get the base theme files from the new version of FusionAuth. The easiest way to do this before upgrading your production version is to install the new version of FusionAuth on your local machine or a VM using Docker. Instructions for installing FusionAuth using Docker can be found in the https://fusionauth.io/docs/v1/tech/installation-guide/docker#docker-compose[FusionAuth Docker Installation Guide].
+Once this has completed downloading, you'll need to get the base theme files from the new version of FusionAuth. The easiest way to do this before upgrading your production version is to install the new version of FusionAuth on your local machine or a VM using Docker. Instructions for installing FusionAuth using Docker can be found in the link:/docs/v1/tech/installation-guide/docker#docker-compose[FusionAuth Docker Installation Guide].
 
-Once you've got the new version of FusionAuth running, you can update the Theme Helper `.env` file in the Theme Helper repo to point to the new version of FusionAuth. You'll need to update the `FUSIONAUTH_URL` to `http://localhost:9011`. You'll also need to login to the new FusionAuth to create an API key, and copy the default theme ID into `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
+Once you've got the new version of FusionAuth running, you can update the Theme Helper `.env` file in the Theme Helper repo to point to the new version of FusionAuth. You'll need to update the `FUSIONAUTH_URL` to `\http://localhost:9011`. You'll also need to login to the new FusionAuth to create an API key, and copy the default theme ID into `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
 
 Now you can run the `download.sh` script again to download the new theme files to the `TMP_DIR` directory.
 

From 31fd27603098f474dba9a01f7a613699741b5fdd Mon Sep 17 00:00:00 2001
From: worktheclock <85885287+worktheclock@users.noreply.github.com>
Date: Thu, 22 Jun 2023 07:41:12 +0200
Subject: [PATCH 25/55] Theme upgrade language edit

---
 .../installation-guide/_theme-upgrade.adoc    | 24 +++++++++++--------
 1 file changed, 14 insertions(+), 10 deletions(-)

diff --git a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
index f6b3cda70e..217313a7a0 100644
--- a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
+++ b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
@@ -1,6 +1,6 @@
 === Templates
 
-When new functionality is introduced to link:/docs/v1/tech/core-concepts/integration-points#hosted-login-pages[the hosted login pages], new theme templates are occasionally added. They are added to the default theme by the upgrade process, but if you've customized your theme to fit your brand, you'll need to modify the theme to have the new template.
+When new functionality is introduced to link:/docs/v1/tech/core-concepts/integration-points#hosted-login-pages[the hosted login pages], new theme templates are occasionally added. They are added to the default theme by the upgrade process but if you've customized your theme to fit your brand, you'll need to modify the theme to have the new template.
 
 In the version release notes, any new templates and macros are documented. If there are changes, you'll want to take a closer look at the themes post upgrade.
 
@@ -8,7 +8,7 @@ As part of your upgrade testing, open the administrative user interface and navi
 
 If any themes are missing templates, they will show as "Upgrade Required". Port the new theme files over to your custom theme, modify them as needed, and save the theme.
 
-In some cases, existing templates are modified. If you have customized your theme, you'll need to compare the new template to your existing versions base theme, and port over any changes to your customized theme. The easiest way to do this is to use a diff tool to compare the two sets of files. Here is a suggested process, before you upgrade:
+In some cases, existing templates are modified. If you have customized your theme, you'll need to compare the new template to your existing version's base theme and port over any changes to your customized theme. The easiest way to do this is to use a diff tool to compare the two sets of files. Here is a suggested process to follow before you upgrade:
 
 1. Download the default theme from your existing version of FusionAuth.
 2. Download the default theme from the new version of FusionAuth.
@@ -19,26 +19,30 @@ You can use the link:https://github.com/FusionAuth/fusionauth-theme-helper[Theme
 
 ==== Using the Theme Helper to Upgrade Themes
 
-Clone the link:https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] repo and follow the install instructions in the `README.md` file. Now, you'll need to download the base themes from your existing version of FusionAuth and the new version of FusionAuth to compare.
+Clone the link:https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] repo and follow the install instructions in the `README.md` file. 
 
-To get the existing version's theme files, create a `.env` file from the `.env.sample` file. Create an link:/docs/v1/tech/apis/authentication#managing-api-keys[API key] with read permissions for Themes in the FusionAuth administrative user interface. Add the API key to the `.env` file. Navigate to [breadcrumb]#Customizations -> Themes# and copy the ID of the default "FusionAuth" theme. Use this value to update the `THEME_ID` key in the .env file.
+Download the base themes from your existing version of FusionAuth and the new version of FusionAuth to compare.
+
+To get the existing version's theme files, create a `.env` file from the `.env.sample` file. Create an link:/docs/v1/tech/apis/authentication#managing-api-keys[API key] with read permissions for Themes in the FusionAuth administrative user interface. Add the API key to the `.env` file. Navigate to [breadcrumb]#Customizations -> Themes# and copy the Id of the default "FusionAuth" theme. Use this value to update the `THEME_ID` key in the `.env` file.
 
 In the `.env` file, set the `FUSIONAUTH_URL` to the URL of your existing FusionAuth instance. Finally, update the `TMP_DIR` to a directory on your local machine where you want the existing theme files to be downloaded, such as `current-theme`.
 
 Now you can run the `download.sh` script to download the existing theme files to the `TMP_DIR` directory.
 
-Once this has completed downloading, you'll need to get the base theme files from the new version of FusionAuth. The easiest way to do this before upgrading your production version is to install the new version of FusionAuth on your local machine or a VM using Docker. Instructions for installing FusionAuth using Docker can be found in the link:/docs/v1/tech/installation-guide/docker#docker-compose[FusionAuth Docker Installation Guide].
+Once the download is complete, you'll need to get the base theme files from the new version of FusionAuth. The easiest way to do this before upgrading your production version is to install the new version of FusionAuth on your local machine or a VM using Docker. Instructions for installing FusionAuth using Docker can be found in the link:/docs/v1/tech/installation-guide/docker#docker-compose[FusionAuth Docker Installation Guide].
+
+Once you've got the new version of FusionAuth running, you can update the Theme Helper `.env` file in the Theme Helper repo to point to the new version of FusionAuth. You'll need to update the `FUSIONAUTH_URL` to `\http://localhost:9011`. 
 
-Once you've got the new version of FusionAuth running, you can update the Theme Helper `.env` file in the Theme Helper repo to point to the new version of FusionAuth. You'll need to update the `FUSIONAUTH_URL` to `\http://localhost:9011`. You'll also need to login to the new FusionAuth to create an API key, and copy the default theme ID into `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
+Log in to the new version of FusionAuth to create an API key and copy the default theme Id into the `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
 
 Now you can run the `download.sh` script again to download the new theme files to the `TMP_DIR` directory.
 
-Once you have both sets of theme files downloaded, you can run the `diff-themes.sh` script to compare the two sets of files. The script takes 2 arguments, the first is the path to the existing theme files, and the second is the path to the new theme files. For example:
+Once you have both sets of theme files downloaded, you can run the `diff-themes.sh` script to compare the two sets of files. The script takes two arguments: the path to the existing theme files and the path to the new theme files. For example:
 
 ```sh
 ./diff-themes.sh current-theme new-theme
 ```
-The script will output a list of files that are different between the two sets of theme files, along with the differences. You can use this list to update your customized theme files. While you can directly use this output to find the changes, it might be useful to use a visual diff tool of your choice to help you make the changes, using the file list as a guide.
+The script will output a list of files that show differences between the two sets of theme files and the differences. You can use this list to update your customized theme files. While you can directly use this output to find the changes, it might be useful to use a visual diff tool to help you make the changes, using the file list as a guide.
 
 === Messages
 
@@ -52,7 +56,7 @@ Missing required keys. See text area below for default English translations. To
 
 FusionAuth warns you about missing required keys in order to avoid an inadvertent bad user experience. The default display for keys with no valid values in theme [field]#Messages# is the key text, such as `[ExternalAuthenticationException]LinkedInToken`, which can be confusing for end users. 
 
-During an upgrade, you can find these keys by testing the upgrade on a development instance or comparing releases in the link:https://github.com/FusionAuth/fusionauth-localization/[fusionauth-localization] repo. You can safely add these new key values to your theme prior to an upgrade. Any unused messages in a theme's `messages` file are silently ignored (unless malformed). 
+During an upgrade, you can find these keys by testing the upgrade on a development instance or comparing releases in the link:https://github.com/FusionAuth/fusionauth-localization/[fusionauth-localization repo]. You can safely add these new key values to your theme prior to an upgrade. Any unused messages in a theme's `messages` file are silently ignored (unless malformed). 
 
-The extra lines won't do any harm, and will ensure an excellent end user experience if they stumble on new functionality right after an upgrade.
+The extra lines won't do any harm and will ensure an excellent end-user experience if a user stumbles on new functionality right after an upgrade.
 

From 006456693b5ae313452cf5772c496fa16ce943b0 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Thu, 22 Jun 2023 17:32:21 +0200
Subject: [PATCH 26/55] added default theme ID in text

---
 site/docs/v1/tech/installation-guide/_theme-upgrade.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
index 217313a7a0..5641f13219 100644
--- a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
+++ b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
@@ -23,7 +23,7 @@ Clone the link:https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helpe
 
 Download the base themes from your existing version of FusionAuth and the new version of FusionAuth to compare.
 
-To get the existing version's theme files, create a `.env` file from the `.env.sample` file. Create an link:/docs/v1/tech/apis/authentication#managing-api-keys[API key] with read permissions for Themes in the FusionAuth administrative user interface. Add the API key to the `.env` file. Navigate to [breadcrumb]#Customizations -> Themes# and copy the Id of the default "FusionAuth" theme. Use this value to update the `THEME_ID` key in the `.env` file.
+To get the existing version's theme files, create a `.env` file from the `.env.sample` file. Create an link:/docs/v1/tech/apis/authentication#managing-api-keys[API key] with read permissions for Themes in the FusionAuth administrative user interface. Add the API key to the `.env` file. The FusionAuth link:/docs/v1/tech/reference/limitations#default-configuration[default theme has the same ID `75a068fd-e94b-451a-9aeb-3ddb9a3b5987`] across all instances. Use this value to update the `THEME_ID` key in the `.env` file.
 
 In the `.env` file, set the `FUSIONAUTH_URL` to the URL of your existing FusionAuth instance. Finally, update the `TMP_DIR` to a directory on your local machine where you want the existing theme files to be downloaded, such as `current-theme`.
 
@@ -33,7 +33,7 @@ Once the download is complete, you'll need to get the base theme files from the
 
 Once you've got the new version of FusionAuth running, you can update the Theme Helper `.env` file in the Theme Helper repo to point to the new version of FusionAuth. You'll need to update the `FUSIONAUTH_URL` to `\http://localhost:9011`. 
 
-Log in to the new version of FusionAuth to create an API key and copy the default theme Id into the `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
+Log in to the new version of FusionAuth to create an API key and copy the link:/docs/v1/tech/reference/limitations#default-configuration[default theme ID `75a068fd-e94b-451a-9aeb-3ddb9a3b5987`] into the `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
 
 Now you can run the `download.sh` script again to download the new theme files to the `TMP_DIR` directory.
 

From 6b06c536f815eeb3c5453accedcdc8bb6e4f6bae Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Tue, 27 Jun 2023 16:45:04 +0200
Subject: [PATCH 27/55] outstanding change requests

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 22 +++++++++++++++-------
 1 file changed, 15 insertions(+), 7 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 124549afc6..ff26b429cf 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -82,7 +82,11 @@ Plan for any downtime or maintenance windows required for the upgrade. If change
 
 FusionAuth can perform database migrations automatically and silently using a process called link:/docs/v1/tech/guides/silent-mode[Silent Mode]. 
 
-If you want to run the migrations interactively, use link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode], or you can run any needed scripts out of band (meaning directly on the database yourself).
+If you want to run the migrations interactively, you can run any needed scripts out of band (meaning directly on the database yourself). The general process would be to: 
+
+- Remove all server nodes from a load balancer/proxy
+- Running the database migration scripts
+- Add all server nodes back to the load balancer/proxy
 
 [NOTE]
 ====
@@ -99,7 +103,9 @@ In general, client libraries are forward compatible, but any issues will be note
 
 === Skipping Versions 
 
-Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. This is called a "version jump". FusionAuth migration can run all the necessary database migrations to get you to the latest version. However, we recommend that you don't skip minor versions and rather migrate from one minor version to the next, step by step. For example, if you are on version 1.37 and want to get to version 1.43, we recommend that you upgrade each minor step to 1.43.
+Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. This is called a "version jump". Version Jumps include minor versions. FusionAuth migration can run all the necessary database migrations to get you to the latest version. In some cases version jumps are safe to do. To determine if you can perform a version jump, you should review the link:/docs/v1/tech/release-notes[release notes] carefully. If the releases focus on bug fixes and minor improvements, you can probably perform a version jump safely. Additionally, if the only changes are to features that you are not using, you can probably perform a version jump.
+
+Whichever approach you take, you should always test the upgrade in a staging environment to identify potential issues. This is particularly important on more complex upgrades involving multiple version jumps or if you have made customizations to FusionAuth. We recommend that the staging environment be as close as possible to your production environment. This includes using the same data, or at least the same data volume as production. This enables you to test both functionality changes and data update performance times before committing to the upgrade on production.
 
 === Migrating Configuration Between Environments
 
@@ -153,7 +159,7 @@ There is still some downtime with this procedure, but it is limited to the time
 
 A blue-green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue-green deployment instead of performing a rolling upgrade isolates the upgrade process from the production environment, reducing the impact and risk to the current production environment.
 
-To perform a blue-green deployment with a three-node cluster, first create three new nodes. Add one of these nodes to the existing cluster. At this point, the new node will lock the database and own it while it completes the database upgrade. The original nodes might give errors, as they will not have access to the database. They can be removed. The remaining new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
+To perform a blue-green deployment with a three-node cluster, first create three new nodes with the new version of FusionAuth on each of them. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. The original nodes might give errors, as they will not have access to the database. They can be removed. The new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
 
 ++++
 {% plantuml source: _diagrams/docs/admin-guide/blue_green_upgrade.plantuml, alt: "Blue green deployment." %}
@@ -161,7 +167,9 @@ To perform a blue-green deployment with a three-node cluster, first create three
  
 === Out-of-Band Database Upgrades
 
-While FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode] or interactively using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode], you may want to perform the database upgrade yourself. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. The scripts for the database migrations are available in the FusionAuth upgrade packages. 
+While FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode]. It can also handle updates interactively on development environments using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode]. Note that Maintenance Mode should never be used in production.
+
+In production, you may want to perform the database upgrade manually. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. Upgrading the database manually involves running SQL scripts directly on your database to update the database schema. 
 
 Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the https://fusionauth.io/direct-download[Direct Downloads] page.
 
@@ -238,10 +246,10 @@ Q: What is runtime mode and how does it affect upgrades? +
 A: FusionAuth runtime mode can be either `production` or `development`. When in the `development` runtime mode, Maintenance Mode will interactively assist you to configure the database and connect to Elasticsearch, if configured. Once you move FusionAuth into production, it is recommended that you modify the runtime mode to `production`. When in `production` runtime mode, Maintenance Mode will no longer be available to you, which means you can be certain that your end users will not find themselves on the database upgrade panel during an upgrade. When in `production` mode, you will either need to leverage Silent Mode to automatically apply database migrations or you will need to apply the database migrations yourself (either by hand or via a script of some sort). For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide].
 
 Q: What is Maintenance Mode? +
-A: Maintenance Mode is a special admin interface for FusionAuth that helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. 
+A: Maintenance Mode is a special admin interface for development environment FusionAuth installations that helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. Note that Maintenance Mode should never be used in production.
 
 Q: What is Silent Mode? +
-A: link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments or for when you want to upgrade FusionAuth without using the Maintenance Mode interface. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in `production` runtime mode too. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will switch to the manual Maintenance Mode interface.
+A: link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in the `production` runtime mode too. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will display an error message on the login page. You should always test your database migrations in a non-production / staging environment before deploying to production.
 
 Q: How many versions can I skip? +
 A: We recommended migrating from one minor version to the next. 
@@ -463,7 +471,7 @@ On Linux in a production environment, use `.deb` or `.rpm` packages. If your pro
 ====
 If you want FusionAuth to upgrade the database automatically, use the link:/docs/v1/tech/guides/silent-mode[Silent Mode] process, which will perform an automated upgrade.
 
-If you want to use Maintenance Mode, ensure your runtime mode is set to `development` and Silent Mode is set to `false`.
+If you want to use Maintenance Mode, ensure your runtime mode is set to `development` and Silent Mode is set to `false`. Maintenance Mode should never be used in a production environment, as is only intended for use in development environments.
 
 If you want to upgrade the database manually, follow the instructions below.
 

From 612e0541dcb9a34bbe848790cbf5ca02725e4543 Mon Sep 17 00:00:00 2001
From: worktheclock <85885287+worktheclock@users.noreply.github.com>
Date: Thu, 29 Jun 2023 12:58:08 +0200
Subject: [PATCH 28/55] Upgrade Guide change requests language edit

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 28 ++++++++++++----------
 1 file changed, 16 insertions(+), 12 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index ff26b429cf..c906d92b6f 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -84,9 +84,9 @@ FusionAuth can perform database migrations automatically and silently using a pr
 
 If you want to run the migrations interactively, you can run any needed scripts out of band (meaning directly on the database yourself). The general process would be to: 
 
-- Remove all server nodes from a load balancer/proxy
-- Running the database migration scripts
-- Add all server nodes back to the load balancer/proxy
+- Remove all server nodes from a load balancer/proxy.
+- Run the database migration scripts.
+- Add all server nodes back to the load balancer/proxy.
 
 [NOTE]
 ====
@@ -99,13 +99,15 @@ The timing of the database upgrade is also important to note. When an upgraded n
 
 Consider that a FusionAuth server upgrade might mean that you need to upgrade your client libraries too. Check if this is needed before upgrading, as it will entail a more complex upgrade process and may require more downtime.
 
-In general, client libraries are forward compatible, but any issues will be noted in the release notes. (Read the release notes carefully.)
+In general, client libraries are forward-compatible, but any issues will be noted in the release notes. (Read the release notes carefully.)
 
 === Skipping Versions 
 
-Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. This is called a "version jump". Version Jumps include minor versions. FusionAuth migration can run all the necessary database migrations to get you to the latest version. In some cases version jumps are safe to do. To determine if you can perform a version jump, you should review the link:/docs/v1/tech/release-notes[release notes] carefully. If the releases focus on bug fixes and minor improvements, you can probably perform a version jump safely. Additionally, if the only changes are to features that you are not using, you can probably perform a version jump.
+Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. This is called a "version jump". Version jumps include minor versions. FusionAuth migration can run all the necessary database migrations to get you to the latest version. 
 
-Whichever approach you take, you should always test the upgrade in a staging environment to identify potential issues. This is particularly important on more complex upgrades involving multiple version jumps or if you have made customizations to FusionAuth. We recommend that the staging environment be as close as possible to your production environment. This includes using the same data, or at least the same data volume as production. This enables you to test both functionality changes and data update performance times before committing to the upgrade on production.
+In some cases, version jumps are safe to do. To determine if you can perform a version jump, you should review the link:/docs/v1/tech/release-notes[release notes] carefully. If the releases focus on bug fixes and minor improvements, you can probably perform a version jump safely. Additionally, if the only changes are to features that you are not using, you can probably perform a version jump.
+
+Whichever approach you take, you should always test the upgrade in a staging environment to identify potential issues. This is particularly important on more complex upgrades involving multiple version jumps or if you have made customizations to FusionAuth. We recommend that the staging environment be as close as possible to your production environment. This includes using the same data, or at least the same data volume, as production. This enables you to test both functionality changes and data update performance times before committing to the upgrade on production.
 
 === Migrating Configuration Between Environments
 
@@ -144,7 +146,7 @@ You can choose to run in-place upgrades on each node or to replace each node wit
 
 A rolling upgrade procedure might look like this:
 - Stop the first node and remove it from the load balancer.
-- Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depend on the code paths being updated as well as how users interact with the system. They should be minimal.
+- Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. They should be minimal.
 - Start the first node and add it back to the load balancer.
 - Stop the second and third nodes, remove them from the load balancer, and upgrade them. 
 - Start the second and third nodes and add them back to the load balancer.
@@ -159,7 +161,7 @@ There is still some downtime with this procedure, but it is limited to the time
 
 A blue-green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue-green deployment instead of performing a rolling upgrade isolates the upgrade process from the production environment, reducing the impact and risk to the current production environment.
 
-To perform a blue-green deployment with a three-node cluster, first create three new nodes with the new version of FusionAuth on each of them. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. The original nodes might give errors, as they will not have access to the database. They can be removed. The new nodes can then be added to the cluster. The system will be down for the duration of the database upgrade, but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
+To perform a blue-green deployment with a three-node cluster, first create three new nodes with the new version of FusionAuth on each of them. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. The original nodes might give errors as they will not have access to the database. These original nodes can be removed. Now add the new nodes to the cluster. The system will be down for the duration of the database upgrade but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
 
 ++++
 {% plantuml source: _diagrams/docs/admin-guide/blue_green_upgrade.plantuml, alt: "Blue green deployment." %}
@@ -167,7 +169,7 @@ To perform a blue-green deployment with a three-node cluster, first create three
  
 === Out-of-Band Database Upgrades
 
-While FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode]. It can also handle updates interactively on development environments using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode]. Note that Maintenance Mode should never be used in production.
+FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode]. FusionAuth can also handle updates interactively on development environments using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode]. Note that Maintenance Mode should never be used in production.
 
 In production, you may want to perform the database upgrade manually. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. Upgrading the database manually involves running SQL scripts directly on your database to update the database schema. 
 
@@ -248,8 +250,10 @@ A: FusionAuth runtime mode can be either `production` or `development`. When in
 Q: What is Maintenance Mode? +
 A: Maintenance Mode is a special admin interface for development environment FusionAuth installations that helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. Note that Maintenance Mode should never be used in production.
 
+A: Maintenance Mode is a special admin interface for FusionAuth installations in development environments. Maintenance Mode helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. Note that Maintenance Mode should never be used in production.
+
 Q: What is Silent Mode? +
-A: link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in the `production` runtime mode too. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will display an error message on the login page. You should always test your database migrations in a non-production / staging environment before deploying to production.
+A: link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in the `production` runtime mode too. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will display an error message on the login page. You should always test your database migrations in a non-production or staging environment before deploying to production.
 
 Q: How many versions can I skip? +
 A: We recommended migrating from one minor version to the next. 
@@ -413,7 +417,7 @@ net start FusionAuthApp
 
 [NOTE]
 ====
-Prior to version 1.37.0 you can find `FusionAuthApp.exe` at:
+Prior to version 1.37.0, you can find `FusionAuthApp.exe` at:
 
 `\fusionauth\fusionauth-app\apache-tomcat\bin\FusionAuthApp.exe`
 
@@ -471,7 +475,7 @@ On Linux in a production environment, use `.deb` or `.rpm` packages. If your pro
 ====
 If you want FusionAuth to upgrade the database automatically, use the link:/docs/v1/tech/guides/silent-mode[Silent Mode] process, which will perform an automated upgrade.
 
-If you want to use Maintenance Mode, ensure your runtime mode is set to `development` and Silent Mode is set to `false`. Maintenance Mode should never be used in a production environment, as is only intended for use in development environments.
+If you want to use Maintenance Mode, ensure your runtime mode is set to `development` and Silent Mode is set to `false`. Maintenance Mode should never be used in a production environment, as it is only intended for use in development environments.
 
 If you want to upgrade the database manually, follow the instructions below.
 

From 20d03d561af77ec79c1461fac1efa04513c52965 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Thu, 29 Jun 2023 16:17:19 +0200
Subject: [PATCH 29/55] simplified and removed duplication from main database
 section

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 11 +----------
 1 file changed, 1 insertion(+), 10 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index c906d92b6f..1c5ba1384c 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -471,22 +471,13 @@ On Linux in a production environment, use `.deb` or `.rpm` packages. If your pro
 
 === Database
 
-[NOTE]
-====
 If you want FusionAuth to upgrade the database automatically, use the link:/docs/v1/tech/guides/silent-mode[Silent Mode] process, which will perform an automated upgrade.
 
-If you want to use Maintenance Mode, ensure your runtime mode is set to `development` and Silent Mode is set to `false`. Maintenance Mode should never be used in a production environment, as it is only intended for use in development environments.
-
 If you want to upgrade the database manually, follow the instructions below.
 
-For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide].
-
-For more information on the various configuration options, see the link:/docs/v1/tech/reference/configuration[Configuration Reference].
-====
-
 [NOTE]
 ====
-You should always back up your database before upgrading using Maintenance Mode.
+You should always back up your database before upgrading using any method.
 ====
 
 Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the https://fusionauth.io/direct-download[Direct Downloads] page.

From 5f7e4051cc4c408b59ff16dab8376322a5c73128 Mon Sep 17 00:00:00 2001
From: Tatenda <31291528+rideam@users.noreply.github.com>
Date: Thu, 29 Jun 2023 16:30:41 +0200
Subject: [PATCH 30/55] fix table of contents

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 29 ++++++++++++++--------
 1 file changed, 18 insertions(+), 11 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 1c5ba1384c..2fdae6a77f 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -31,11 +31,12 @@ Topics covered in this document:
 ** <<Out-of-Band Database Upgrades>>
 * <<FAQs>>
 * <<Detailed Upgrade Instructions>>
-* <<ZIP Packages>>
-* <<Linux Packages>>
-** <<Troubleshooting Upgrade with RPMs>>
-* <<FastPath>>
-* <<Database>>
+** <<Docker>>
+** <<Homebrew>>
+** <<ZIP Packages>>
+** <<Linux Packages>>
+** <<FastPath>>
+** <<Database>>
 
 == When to Upgrade
 
@@ -93,7 +94,7 @@ If you want to run the migrations interactively, you can run any needed scripts
 You should always back up your database before using Maintenance Mode or performing any database migrations by any method.
 ====
 
-The timing of the database upgrade is also important to note. When an upgraded node is added to a FusionAuth cluster, it will lock the database and perform the database upgrade if configured for Silent Mode and the database requires upgrading. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. 
+The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for Silent Mode and the database requires upgrading. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete.
 
 === Connected Applications and Client Libraries
 
@@ -113,10 +114,10 @@ Whichever approach you take, you should always test the upgrade in a staging env
 
 There are a number of options for managing the configuration of your FusionAuth instance over time and promoting changes from one environment to another. These include:
 
-- Script the changes
-- Terraform
-- Pulumi
-- Manual configuration via the UI
+- Script the changes.
+- Terraform.
+- Pulumi.
+- Manual configuration via the UI.
 
 You can read more in link:/docs/v1/tech/admin-guide/configuration-management[the Configuration Management guide].
 
@@ -145,6 +146,7 @@ Because individual nodes are taken offline during the rolling update, the capaci
 You can choose to run in-place upgrades on each node or to replace each node with a new node running the latest version of FusionAuth. In-place upgrades are potentially faster, but if something goes wrong, you may need to roll back the upgrade. Replacing nodes may be slower, but if something goes wrong, you can simply revert to the previous version of FusionAuth by pointing the load balancer to the old nodes.
 
 A rolling upgrade procedure might look like this:
+
 - Stop the first node and remove it from the load balancer.
 - Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. They should be minimal.
 - Start the first node and add it back to the load balancer.
@@ -169,7 +171,12 @@ To perform a blue-green deployment with a three-node cluster, first create three
  
 === Out-of-Band Database Upgrades
 
-FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode]. FusionAuth can also handle updates interactively on development environments using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode]. Note that Maintenance Mode should never be used in production.
+FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode]. FusionAuth can also handle updates interactively on development environments using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode].
+
+[WARNING]
+====
+Note that Maintenance Mode should never be used in production.
+====
 
 In production, you may want to perform the database upgrade manually. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. Upgrading the database manually involves running SQL scripts directly on your database to update the database schema. 
 

From 7d819106d079fdefbd5ac1a17c8df11bd7acf5ed Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Thu, 29 Jun 2023 16:40:17 +0200
Subject: [PATCH 31/55] removed second db update section, added backup warning
 to out of band section

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 89 ++--------------------
 1 file changed, 7 insertions(+), 82 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 2fdae6a77f..766779ac10 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -36,7 +36,6 @@ Topics covered in this document:
 ** <<ZIP Packages>>
 ** <<Linux Packages>>
 ** <<FastPath>>
-** <<Database>>
 
 == When to Upgrade
 
@@ -178,7 +177,13 @@ FusionAuth can handle database migrations automatically using link:/docs/v1/tech
 Note that Maintenance Mode should never be used in production.
 ====
 
-In production, you may want to perform the database upgrade manually. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. Upgrading the database manually involves running SQL scripts directly on your database to update the database schema. 
+[NOTE]
+====
+You should always back up your database before upgrading regardless of the upgrade method you choose.
+====
+
+
+In production, you may want to perform the database upgrade manually, also known as an out-of-band upgrade. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. Upgrading the database manually involves running SQL scripts directly on your database to update the database schema. 
 
 Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the https://fusionauth.io/direct-download[Direct Downloads] page.
 
@@ -255,8 +260,6 @@ Q: What is runtime mode and how does it affect upgrades? +
 A: FusionAuth runtime mode can be either `production` or `development`. When in the `development` runtime mode, Maintenance Mode will interactively assist you to configure the database and connect to Elasticsearch, if configured. Once you move FusionAuth into production, it is recommended that you modify the runtime mode to `production`. When in `production` runtime mode, Maintenance Mode will no longer be available to you, which means you can be certain that your end users will not find themselves on the database upgrade panel during an upgrade. When in `production` mode, you will either need to leverage Silent Mode to automatically apply database migrations or you will need to apply the database migrations yourself (either by hand or via a script of some sort). For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide].
 
 Q: What is Maintenance Mode? +
-A: Maintenance Mode is a special admin interface for development environment FusionAuth installations that helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. Note that Maintenance Mode should never be used in production.
-
 A: Maintenance Mode is a special admin interface for FusionAuth installations in development environments. Maintenance Mode helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. Note that Maintenance Mode should never be used in production.
 
 Q: What is Silent Mode? +
@@ -476,81 +479,3 @@ While FastPath is an option to perform an upgrade, the FastPath process limits t
 
 On Linux in a production environment, use `.deb` or `.rpm` packages. If your production platform is macOS or Windows, please manually manage the upgrade using the `.zip` bundles.
 
-=== Database
-
-If you want FusionAuth to upgrade the database automatically, use the link:/docs/v1/tech/guides/silent-mode[Silent Mode] process, which will perform an automated upgrade.
-
-If you want to upgrade the database manually, follow the instructions below.
-
-[NOTE]
-====
-You should always back up your database before upgrading using any method.
-====
-
-Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the https://fusionauth.io/direct-download[Direct Downloads] page.
-
-[WARNING]
-====
-When upgrading your database from a previous version, be sure to only run the scripts located in the `migrations` folder. The base files
- `mysql.sql` and `postgresql.sql` should only be used during a clean installation when no database schema is present.
-====
-
-Find the FusionAuth migrations in the Database Schema ZIP file. Run them in order, starting with the first migration greater than the version you are coming from, and ending with the version that is less than or equal to the target upgrade version.
-
-For example, if upgrading from version `1.19.1` to `1.22.0`, run the following SQL migrations in this order:
-
-* `1.20.0.sql`
-* `1.21.0.sql`
-* `1.22.0.sql`
-
-[source]
-----
-fusionauth-database-schema/
-|-- migrations/
-    |--  [mysql | postgresql]/
-      |-- 1.1.0.sql
-      |-- 1.2.0.sql
-      |-- 1.3.0.sql
-      |-- 1.3.1.sql
-      |-- 1.5.0.sql
-      |-- 1.6.0.sql
-      |-- 1.7.0.sql
-      |-- 1.7.1.sql
-      |-- 1.8.0-RC.1.sql
-      |-- 1.8.1-RC.1.sql
-      |-- 1.11.0.sql
-      |-- 1.12.0.sql
-      |-- 1.13.0.sql
-      |-- 1.14.0.sql
-      |-- 1.15.0.sql
-      |-- 1.15.3.sql
-      |-- 1.16.0-RC.1.sql
-      |-- 1.16.0.sql
-      |-- 1.17.0.sql
-      |-- 1.17.3.sql
-      |-- 1.18.0.sql
-      |-- 1.18.2.sql
-      |-- 1.19.0.sql
-      |-- 1.20.0.sql
-      |-- 1.21.0.sql
-      |-- 1.22.0.sql
-      |-- 1.23.0.sql
-      |-- 1.25.0.sql
-      |-- 1.26.0.sql
-      |-- 1.27.0.sql
-      |-- 1.28.0.sql
-      |-- 1.28.1.sql
-      |-- 1.29.1.sql
-      |-- 1.30.0.sql
-      |-- 1.30.1.sql
-      |-- 1.30.2.sql
-      |-- 1.32.0.sql
-      |-- 1.33.0.sql
-      |-- 1.35.0.sql
-      |-- 1.36.0.sql
-      |-- 1.37.0.sql
-      |-- 1.40.1.sql
-      |-- 1.41.0.sql
-      |-- 1.43.0.sql
-      |-- 1.44.0.sql
-----

From 5f42c7238f9d03ee2c1d72e3b4e10aac5bdbe014 Mon Sep 17 00:00:00 2001
From: Tatenda <31291528+rideam@users.noreply.github.com>
Date: Thu, 29 Jun 2023 16:55:55 +0200
Subject: [PATCH 32/55] fix note

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 766779ac10..2fe1a27931 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -172,13 +172,11 @@ To perform a blue-green deployment with a three-node cluster, first create three
 
 FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode]. FusionAuth can also handle updates interactively on development environments using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode].
 
+
 [WARNING]
 ====
 Note that Maintenance Mode should never be used in production.
-====
 
-[NOTE]
-====
 You should always back up your database before upgrading regardless of the upgrade method you choose.
 ====
 

From 72d7e3f40d23ec8050ff8c13e5e7856d974b93be Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Tue, 1 Aug 2023 10:11:22 +0200
Subject: [PATCH 33/55] Update site/docs/v1/tech/admin-guide/upgrade.adoc

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 2fe1a27931..a80abcd060 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -59,6 +59,7 @@ You might want to delay upgrading in the following situations:
 
 You can stay informed about new FusionAuth releases and updates by:
 
+* Signing up for link:/docs/v1/tech/admin-guide/releases[release notifications].
 * Monitoring the link:/docs/v1/tech/release-notes[release notes].
 * Joining the https://fusionauth.io/community[FusionAuth community] forum and/or slack.
 * Following FusionAuth on social media platforms, including https://twitter.com/FusionAuth[Twitter] and https://www.linkedin.com/company/fusionauth[LinkedIn].

From 8c9f209389fd8d17755ea8f1eaefbf8cc2cafcd1 Mon Sep 17 00:00:00 2001
From: Gareth Dwyer <sixhobbits@users.noreply.github.com>
Date: Tue, 1 Aug 2023 10:16:24 +0200
Subject: [PATCH 34/55] Apply suggestions from code review

Co-authored-by: Dan Moore <dan@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc    | 50 +++++++++++--------
 .../installation-guide/_theme-upgrade.adoc    |  8 +--
 2 files changed, 33 insertions(+), 25 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index a80abcd060..ea9ab1fdbe 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -79,7 +79,7 @@ Before starting the upgrade process on production, test the upgrade in a staging
 
 === Downtime and Database Migrations
 
-Plan for any downtime or maintenance windows required for the upgrade. If changes to the database schema are required, this could require more steps and downtime that affects end users. Such changes are always noted in the release notes. (Read the release notes carefully.) A pure application upgrade, on the other hand, may not require any downtime from an end-user perspective.
+Plan for any downtime or maintenance windows required for the upgrade. If changes to the database schema are required, this could require more steps and downtime that affects end users. Such changes are always noted in the release notes. (Read the release notes carefully.) An upgrade without a schema change, on the other hand, may not require any downtime from an end-user perspective.
 
 FusionAuth can perform database migrations automatically and silently using a process called link:/docs/v1/tech/guides/silent-mode[Silent Mode]. 
 
@@ -91,7 +91,7 @@ If you want to run the migrations interactively, you can run any needed scripts
 
 [NOTE]
 ====
-You should always back up your database before using Maintenance Mode or performing any database migrations by any method.
+You should always back up your database before upgrading. Doing so gives you the ability to roll back.
 ====
 
 The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for Silent Mode and the database requires upgrading. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete.
@@ -102,19 +102,24 @@ Consider that a FusionAuth server upgrade might mean that you need to upgrade yo
 
 In general, client libraries are forward-compatible, but any issues will be noted in the release notes. (Read the release notes carefully.)
 
+If you are using an OIDC compatible library in your application to log your users in, it is unlikely that this integration would require modification. But test it out to make sure.
+
 === Skipping Versions 
 
-Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. This is called a "version jump". Version jumps include minor versions. FusionAuth migration can run all the necessary database migrations to get you to the latest version. 
+Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. For example, you might want to upgrade from version 1.43.0 to 1.45.0. This is called a "version jump". Version jumps include minor versions. FusionAuth can run all the necessary database migrations to get you to the latest version, or you can apply the database migrations yourself.
+
+In some cases, version jumps are safe to do. To determine if you can perform a version jump, you should review the link:/docs/v1/tech/release-notes[release notes] carefully. If the releases focus on bug fixes and minor improvements, you can probably perform a version jump safely. Version jumping across patch versions, from 1.43.0 to 1.43.3, for example, is usually safe. Additionally, if the only changes are to features that you are not using, a version jump will work.
 
-In some cases, version jumps are safe to do. To determine if you can perform a version jump, you should review the link:/docs/v1/tech/release-notes[release notes] carefully. If the releases focus on bug fixes and minor improvements, you can probably perform a version jump safely. Additionally, if the only changes are to features that you are not using, you can probably perform a version jump.
+The alternative to a version jump is to migrate and test at each version of FusionAuth. For example, if you were moving from 1.43.0 to 1.45.0, you'd upgrade to 1.43.1 and test, then 1.43.2 and test, then 1.43.3 and test, then 1.44.0 and test, then 1.45.0 and test. This is a good option because if there are any issues, you'll be able to know precisely which version of FusionAuth is problematic. It's a great option if you have automated tests that can exercise FusionAuth integrations.
 
-Whichever approach you take, you should always test the upgrade in a staging environment to identify potential issues. This is particularly important on more complex upgrades involving multiple version jumps or if you have made customizations to FusionAuth. We recommend that the staging environment be as close as possible to your production environment. This includes using the same data, or at least the same data volume, as production. This enables you to test both functionality changes and data update performance times before committing to the upgrade on production.
+
+Whichever approach you take, you should always test the upgrade in a staging environment to identify potential issues. This is particularly important on more complex upgrades where you are moving between distant minor versions (from 1.22.0 to 1.43.0, for example) or if you have made customizations to FusionAuth. We recommend that the staging environment be as close as possible to your production environment. This includes using the same data, or at least the same data volume, as production. This enables you to test both functionality changes and data update performance times before committing to the upgrade on production.
 
 === Migrating Configuration Between Environments
 
 There are a number of options for managing the configuration of your FusionAuth instance over time and promoting changes from one environment to another. These include:
 
-- Script the changes.
+- Script the changes using a client library.
 - Terraform.
 - Pulumi.
 - Manual configuration via the UI.
@@ -131,9 +136,9 @@ include::docs/v1/tech/installation-guide/_theme-upgrade.adoc[]
 
 === Easiest Route
 
-The easiest upgrade route is to simply stop all your services, upgrade everything, and then bring it all back online. 
+The easiest upgrade route is to simply stop all your services, upgrade each FusionAuth instance, and then bring it all back online. 
 
-This is a good option for single-instance development or QA systems, or for systems that can tolerate longer periods of downtime.
+This is a good option for single-instance development or QA systems, or for systems that can tolerate longer periods of downtime. For instance, if you know you have near-zero user activity at midnight, you can upgrade then. If you have scheduled downtime for other components of your system, that is a good time to upgrade FusionAuth in this manner.
 
 If minimizing downtime is a goal, then rolling upgrades or a blue-green deployment might be more suitable. 
 
@@ -143,17 +148,17 @@ You can perform a rolling upgrade if you have three FusionAuth nodes running beh
 
 Because individual nodes are taken offline during the rolling update, the capacity of your installation is reduced during the upgrade.
 
-You can choose to run in-place upgrades on each node or to replace each node with a new node running the latest version of FusionAuth. In-place upgrades are potentially faster, but if something goes wrong, you may need to roll back the upgrade. Replacing nodes may be slower, but if something goes wrong, you can simply revert to the previous version of FusionAuth by pointing the load balancer to the old nodes.
+You can choose to run in-place upgrades on each node or to replace each node with a new node running the latest version of FusionAuth. In-place upgrades are simpler and faster because you don't have to spin up a new server, but if something goes wrong, rolling back the upgrade is more complex. Replacing nodes may be slower, but if something goes wrong, you can revert to the previous version of FusionAuth by pointing the load balancer to the old nodes.
 
-A rolling upgrade procedure might look like this:
+An in-place rolling upgrade procedure might look like this:
 
 - Stop the first node and remove it from the load balancer.
-- Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. They should be minimal.
-- Start the first node and add it back to the load balancer.
+- Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. For core login functionality, they should be minimal.
+- Add the first node back to the load balancer.
 - Stop the second and third nodes, remove them from the load balancer, and upgrade them. 
 - Start the second and third nodes and add them back to the load balancer.
 
-There is still some downtime with this procedure, but it is limited to the time it takes to run the database migration on the upgraded first node. There will be limited capacity during the upgrade, especially while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
+There is still downtime with this procedure, but it is limited to the time it takes to run the first node to run the database migration. There will be limited capacity during the upgrade while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
 
 ++++
 {% plantuml source: _diagrams/docs/admin-guide/rolling_upgrade.plantuml, alt: "Rolling upgrade." %}
@@ -163,7 +168,9 @@ There is still some downtime with this procedure, but it is limited to the time
 
 A blue-green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue-green deployment instead of performing a rolling upgrade isolates the upgrade process from the production environment, reducing the impact and risk to the current production environment.
 
-To perform a blue-green deployment with a three-node cluster, first create three new nodes with the new version of FusionAuth on each of them. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. The original nodes might give errors as they will not have access to the database. These original nodes can be removed. Now add the new nodes to the cluster. The system will be down for the duration of the database upgrade but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
+To perform a blue-green deployment with a three-node cluster, first create three new nodes with the new version of FusionAuth on each of them. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. The original nodes might give errors as they will not have access to the database. These original nodes can be removed from the load balancer. Add the new nodes to the cluster. 
+
+With this approach, the system will be down for the duration of the database upgrade but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
 
 ++++
 {% plantuml source: _diagrams/docs/admin-guide/blue_green_upgrade.plantuml, alt: "Blue green deployment." %}
@@ -173,18 +180,17 @@ To perform a blue-green deployment with a three-node cluster, first create three
 
 FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode]. FusionAuth can also handle updates interactively on development environments using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode].
 
-
 [WARNING]
 ====
-Note that Maintenance Mode should never be used in production.
+Maintenance Mode should never be used in production. You don't want your end users to be prompted to update a database, which is what Maintenance Mode does.
 
 You should always back up your database before upgrading regardless of the upgrade method you choose.
 ====
 
 
-In production, you may want to perform the database upgrade manually, also known as an out-of-band upgrade. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. Upgrading the database manually involves running SQL scripts directly on your database to update the database schema. 
+In production, you may want to perform the database upgrade rather than allow FusionAuth to do so. This is also known as an out-of-band upgrade. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. Upgrading the database involves running SQL scripts to update the database schema. 
 
-Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the https://fusionauth.io/direct-download[Direct Downloads] page.
+Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the link:/direct-download[Direct Downloads] page.
 
 [WARNING]
 ====
@@ -268,11 +274,13 @@ Q: How many versions can I skip? +
 A: We recommended migrating from one minor version to the next. 
 
 Q: How often should I upgrade? +
-A: You can upgrade whenever you want to. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release. In addition, we don't typically backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix.
+A: You can upgrade whenever you want to. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release: within the last three minor versions. In addition, we don't typically backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix. We recommend you set up a regular cadence of reviewing and upgrading FusionAuth that fits your business needs, the same as you would with a framework or library your application depends on.
 
-Q: How can I find out about new releases? +
-A: We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. 
 
+Q: How can I find out about new releases? +
+A: We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. There are a link:/docs/v1/tech/admin-guide/releases[variety of ways to be notified of releases, including an email list and RSS feed].
+Q: Does FusionAuth support zero-downtime upgrades? +
+A: At this time, it does not when there is a database change. While there are a variety of options that can minimize downtime, upgrades will cause downtime whenever a schema change is required. Please https://github.com/FusionAuth/fusionauth-issues/issues/1240[review and upvote this issue] if zero-downtime upgrades are important to you.
 
 == Detailed Upgrade Instructions
 
diff --git a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
index 5641f13219..500e48b2b4 100644
--- a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
+++ b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
@@ -15,11 +15,11 @@ In some cases, existing templates are modified. If you have customized your them
 3. Use a diff tool to compare the two sets of files. 
 4. Apply any differences to your customized theme.
 
-You can use the link:https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] to help  with this process.
+You can use the https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] to help  with this process.
 
 ==== Using the Theme Helper to Upgrade Themes
 
-Clone the link:https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] repo and follow the install instructions in the `README.md` file. 
+Clone the https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] repo and follow the install instructions in the `README.md` file. 
 
 Download the base themes from your existing version of FusionAuth and the new version of FusionAuth to compare.
 
@@ -29,9 +29,9 @@ In the `.env` file, set the `FUSIONAUTH_URL` to the URL of your existing FusionA
 
 Now you can run the `download.sh` script to download the existing theme files to the `TMP_DIR` directory.
 
-Once the download is complete, you'll need to get the base theme files from the new version of FusionAuth. The easiest way to do this before upgrading your production version is to install the new version of FusionAuth on your local machine or a VM using Docker. Instructions for installing FusionAuth using Docker can be found in the link:/docs/v1/tech/installation-guide/docker#docker-compose[FusionAuth Docker Installation Guide].
+Once the download is complete, you'll need to get the base theme files from the new version of FusionAuth. The easiest way to do this is to install the new version of FusionAuth on your local machine or a VM using Docker. Instructions for installing FusionAuth using Docker can be found in the link:/docs/v1/tech/installation-guide/docker#docker-compose[FusionAuth Docker Installation Guide].
 
-Once you've got the new version of FusionAuth running, you can update the Theme Helper `.env` file in the Theme Helper repo to point to the new version of FusionAuth. You'll need to update the `FUSIONAUTH_URL` to `\http://localhost:9011`. 
+Once you've got the new version of FusionAuth running, you can update the Theme Helper `.env` file in the Theme Helper repo to point to the new version of FusionAuth. If running locally, update the `FUSIONAUTH_URL` to `\http://localhost:9011`. 
 
 Log in to the new version of FusionAuth to create an API key and copy the link:/docs/v1/tech/reference/limitations#default-configuration[default theme ID `75a068fd-e94b-451a-9aeb-3ddb9a3b5987`] into the `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
 

From d2e1bdc9bdad32b71ebdb4ccc29bb901a375969e Mon Sep 17 00:00:00 2001
From: Tatenda <31291528+rideam@users.noreply.github.com>
Date: Wed, 2 Aug 2023 12:52:50 +0200
Subject: [PATCH 35/55] feedback updates

---
 site/docs/v1/tech/admin-guide/upgrade.adoc    | 77 ++++++++++++-------
 .../v1/tech/installation-guide/_modes.adoc    |  8 ++
 .../installation-guide/fusionauth-app.adoc    |  6 ++
 3 files changed, 64 insertions(+), 27 deletions(-)
 create mode 100644 site/docs/v1/tech/installation-guide/_modes.adoc

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 6ee07e4e5c..0d79fda7c5 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -94,7 +94,7 @@ If you want to run the migrations interactively, you can run any needed scripts
 You should always back up your database before upgrading. Doing so gives you the ability to roll back.
 ====
 
-The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for Silent Mode and the database requires upgrading. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete.
+The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for link:/docs/v1/tech/guides/silent-mode[Silent Mode] and the database requires upgrading. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete.
 
 === Connected Applications and Client Libraries
 
@@ -134,6 +134,13 @@ include::docs/v1/tech/installation-guide/_theme-upgrade.adoc[]
 
 == Upgrade Options
 
+[WARNING]
+====
+Maintenance Mode should never be used in production. You don't want your end users to be prompted to update a database, which is what Maintenance Mode does.
+
+You should always back up your database before upgrading regardless of the upgrade method you choose.
+====
+
 === Easiest Route
 
 The easiest upgrade route is to simply stop all your services, upgrade each FusionAuth instance, and then bring it all back online. 
@@ -160,8 +167,16 @@ An in-place rolling upgrade procedure might look like this:
 
 There is still downtime with this procedure, but it is limited to the time it takes to run the first node to run the database migration. There will be limited capacity during the upgrade while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
 
+
 ++++
-{% plantuml source: _diagrams/docs/admin-guide/rolling_upgrade.plantuml, alt: "Rolling upgrade." %}
+{% mermaid %}
+graph TB
+    A(Users) --> B(Load Balancer)
+    B --> |Switch traffic when ready <br/> Upgrade one node at a time| C(Node 1)
+    B --> D(Node 2)
+    B --> E(Node 3)
+    style C fill:#C0F0C0
+{% endmermaid %}
 ++++
 
 === Blue-Green Deployment
@@ -172,22 +187,36 @@ To perform a blue-green deployment with a three-node cluster, first create three
 
 With this approach, the system will be down for the duration of the database upgrade but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
 
+
 ++++
-{% plantuml source: _diagrams/docs/admin-guide/blue_green_upgrade.plantuml, alt: "Blue green deployment." %}
+{% mermaid %}
+graph TB
+    A(Users) --> B(Load Balancer)
+    subgraph green [Green Deployment - new version]
+        C(Node 1)
+        D(Node 2)
+        E(Node 3)
+        style C fill:#C0F0C0
+        style D fill:#C0F0C0
+        style E fill:#C0F0C0
+    end
+    subgraph blue [Blue Deployment - old version]
+        F(Node 1)
+        G(Node 2)
+        H(Node 3)
+        style F fill:#add8e6
+        style G fill:#add8e6
+        style H fill:#C0C0F0
+    end
+    B --> |Switch traffic when ready|green
+    B --> blue
+{% endmermaid %}
 ++++
- 
+
 === Out-of-Band Database Upgrades
 
 FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode]. FusionAuth can also handle updates interactively on development environments using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode].
 
-[WARNING]
-====
-Maintenance Mode should never be used in production. You don't want your end users to be prompted to update a database, which is what Maintenance Mode does.
-
-You should always back up your database before upgrading regardless of the upgrade method you choose.
-====
-
-
 In production, you may want to perform the database upgrade rather than allow FusionAuth to do so. This is also known as an out-of-band upgrade. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. Upgrading the database involves running SQL scripts to update the database schema. 
 
 Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the link:/direct-download[Direct Downloads] page.
@@ -264,26 +293,20 @@ fusionauth-database-schema/
 
 == FAQs
 
-Q: What is runtime mode and how does it affect upgrades? +  
-A: FusionAuth runtime mode can be either `production` or `development`. When in the `development` runtime mode, Maintenance Mode will interactively assist you to configure the database and connect to Elasticsearch, if configured. Once you move FusionAuth into production, it is recommended that you modify the runtime mode to `production`. When in `production` runtime mode, Maintenance Mode will no longer be available to you, which means you can be certain that your end users will not find themselves on the database upgrade panel during an upgrade. When in `production` mode, you will either need to leverage Silent Mode to automatically apply database migrations or you will need to apply the database migrations yourself (either by hand or via a script of some sort). For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide].
-
-Q: What is Maintenance Mode? +
-A: Maintenance Mode is a special admin interface for FusionAuth installations in development environments. Maintenance Mode helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. Note that Maintenance Mode should never be used in production.
+include::docs/v1/tech/installation-guide/_modes.adoc[]
 
-Q: What is Silent Mode? +
-A: link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in the `production` runtime mode too. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will display an error message on the login page. You should always test your database migrations in a non-production or staging environment before deploying to production.
+**Q:** How many versions can I skip? +
+**A:** We recommended migrating from one minor version to the next.
 
-Q: How many versions can I skip? +
-A: We recommended migrating from one minor version to the next. 
+**Q:** How often should I upgrade? +
+**A:** You can upgrade whenever you want to. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release: within the last three minor versions. In addition, we don't typically backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix. We recommend you set up a regular cadence of reviewing and upgrading FusionAuth that fits your business needs, the same as you would with a framework or library your application depends on.
 
-Q: How often should I upgrade? +
-A: You can upgrade whenever you want to. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release: within the last three minor versions. In addition, we don't typically backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix. We recommend you set up a regular cadence of reviewing and upgrading FusionAuth that fits your business needs, the same as you would with a framework or library your application depends on.
 
+**Q:** How can I find out about new releases? +
+**A:** We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. There are a link:/docs/v1/tech/admin-guide/releases[variety of ways to be notified of releases, including an email list and RSS feed].
 
-Q: How can I find out about new releases? +
-A: We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. There are a link:/docs/v1/tech/admin-guide/releases[variety of ways to be notified of releases, including an email list and RSS feed].
-Q: Does FusionAuth support zero-downtime upgrades? +
-A: At this time, it does not when there is a database change. While there are a variety of options that can minimize downtime, upgrades will cause downtime whenever a schema change is required. Please https://github.com/FusionAuth/fusionauth-issues/issues/1240[review and upvote this issue] if zero-downtime upgrades are important to you.
+**Q:** Does FusionAuth support zero-downtime upgrades? +
+**A:** At this time, it does not when there is a database change. While there are a variety of options that can minimize downtime, upgrades will cause downtime whenever a schema change is required. Please https://github.com/FusionAuth/fusionauth-issues/issues/1240[review and upvote this issue] if zero-downtime upgrades are important to you.
 
 == Detailed Upgrade Instructions
 
diff --git a/site/docs/v1/tech/installation-guide/_modes.adoc b/site/docs/v1/tech/installation-guide/_modes.adoc
new file mode 100644
index 0000000000..a61427babe
--- /dev/null
+++ b/site/docs/v1/tech/installation-guide/_modes.adoc
@@ -0,0 +1,8 @@
+**Q:** What is runtime mode and how does it affect upgrades? +
+**A:** FusionAuth runtime mode can be either `production` or `development`. When in the `development` runtime mode, Maintenance Mode will interactively assist you to configure the database and connect to Elasticsearch, if configured. Once you move FusionAuth into production, it is recommended that you modify the runtime mode to `production`. When in `production` runtime mode, Maintenance Mode will no longer be available to you, which means you can be certain that your end users will not find themselves on the database upgrade panel during an upgrade. When in `production` mode, you will either need to leverage Silent Mode to automatically apply database migrations or you will need to apply the database migrations yourself (either by hand or via a script of some sort). For more on runtime modes, see the link:/docs/v1/tech/installation-guide/fusionauth-app#runtime-modes[FusionAuth Installation Guide].
+
+**Q:** What is Maintenance Mode? +
+**A:** Maintenance Mode is a special admin interface for FusionAuth installations in development environments. Maintenance Mode helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. Note that Maintenance Mode should never be used in production.
+
+**Q:** What is Silent Mode? +
+**A:** link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in the `production` runtime mode too. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will display an error message on the login page. You should always test your database migrations in a non-production or staging environment before deploying to production.
\ No newline at end of file
diff --git a/site/docs/v1/tech/installation-guide/fusionauth-app.adoc b/site/docs/v1/tech/installation-guide/fusionauth-app.adoc
index 3d490dcee2..bbcb766f87 100644
--- a/site/docs/v1/tech/installation-guide/fusionauth-app.adoc
+++ b/site/docs/v1/tech/installation-guide/fusionauth-app.adoc
@@ -127,6 +127,12 @@ sudo systemctl start fusionauth-app
 net start FusionAuthApp
 ----
 
+
+== FAQs
+
+include::docs/v1/tech/installation-guide/_modes.adoc[]
+
+
 == Runtime Modes
 
 The runtime mode may be configured to trigger or suppress environment specific runtime behavior.

From 259bbc1026d9dff90cbf3a2544b0719b948efcb9 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Thu, 10 Aug 2023 09:55:49 +0200
Subject: [PATCH 36/55] added rollback info and removed vistigal note

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 31 +++++++++++++++++-----
 1 file changed, 25 insertions(+), 6 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 0d79fda7c5..dc8fdc3614 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -94,7 +94,7 @@ If you want to run the migrations interactively, you can run any needed scripts
 You should always back up your database before upgrading. Doing so gives you the ability to roll back.
 ====
 
-The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for link:/docs/v1/tech/guides/silent-mode[Silent Mode] and the database requires upgrading. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete.
+The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for link:/docs/v1/tech/guides/silent-mode[Silent Mode] and the database requires upgrading. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. Learn more about the different runtime modes and how they affect database upgrades in the link:/#FAQs[FAQs] section below.
 
 === Connected Applications and Client Libraries
 
@@ -290,6 +290,26 @@ fusionauth-database-schema/
       |-- 1.47.0.sql
 ----
 
+== Rolling Back an Upgrade
+
+In the event that an upgrade is not successful or causes unexpected issues, you may need to rollback your FusionAuth instance to a previous version. Below are the steps for initiating a rollback:
+
+1.  Stop your FusionAuth instances. 
+2.  Initiate the process to restore from the database backup, which you should have taken prior to starting the upgrade.
+3.  Re-deploy FusionAuth but use the previous version you were using instead of the new one. How you do this will depend on your deployment method. 
+
+If you are running a FusionAuth Cloud deployment, you can find instructions for rolling back an upgrade here: link:/docs/v1/tech/installation-guide/cloud#rolling-back-from-a-problematic-upgrade[Rolling Back from a Problematic Upgrade].
+
+It's import to consider the timing implications of a rollback, or any disaster recovery process. RTO, or Recovery Time Objective, is the targeted duration of time within which a service should be restored after an outage to avoid unacceptable consequences. Simply put, it is how long you can afford to be without the service or system before it greatly impacts your business. It represents the goal for the time taken to recover from failure.
+
+RPO, or Recovery Point Objective, on the other hand, refers to the maximum tolerable amount of data loss measured in time. RPO is determined by looking at the time of the last backup you need to restore from and the restore time. 
+
+In the context of a FusionAuth upgrade rollback, the RPO would be the time since the last backup was taken before the upgrade, and the RTO would be the time it takes to stand up the older version of the system and restore the database. 
+
+The RPO effectively measures the maximum tolerable data loss in the event of a rollback, and the RTO measures the time it takes to recover from the failure.
+
+
+
 
 == FAQs
 
@@ -312,6 +332,9 @@ include::docs/v1/tech/installation-guide/_modes.adoc[]
 
 This section will guide you with detailed technical instructions on how to upgrade FusionAuth nodes on different platforms.
 
+=== Cloud 
+
+To upgrade your FusionAuth Cloud instance, see link:/docs/v1/tech/installation-guide/cloud#upgrading-a-deployment[Cloud Installation Guide].
 
 === Docker
 
@@ -321,14 +344,10 @@ include::docs/v1/tech/shared/_upgrade-using-docker.adoc[]
 
 include::docs/v1/tech/shared/_upgrade-using-brew.adoc[]
 
-[NOTE]
-====
-If you want to use manual mode, download the latest version of FusionAuth and follow the instructions below. See https://fusionauth.io/download[Downloads].
-====
 
 === ZIP Packages
 
-FusionAuth is available in a ZIP package for macOS, Linux, and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth.
+FusionAuth is available in a ZIP package for macOS, Linux, and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth. You can find the ZIP packages at the FusionAuth https://fusionauth.io/download[Downloads] page.
 
 ==== macOS and Linux
 

From 143b37cb3fd358cea408cddbd50858118d32a932 Mon Sep 17 00:00:00 2001
From: Bradley Van Aardt <theminidriver@gmail.com>
Date: Thu, 10 Aug 2023 09:58:14 +0200
Subject: [PATCH 37/55] added intro and links for silent mode

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index dc8fdc3614..5e5926924c 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -94,7 +94,7 @@ If you want to run the migrations interactively, you can run any needed scripts
 You should always back up your database before upgrading. Doing so gives you the ability to roll back.
 ====
 
-The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for link:/docs/v1/tech/guides/silent-mode[Silent Mode] and the database requires upgrading. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. Learn more about the different runtime modes and how they affect database upgrades in the link:/#FAQs[FAQs] section below.
+The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for link:/docs/v1/tech/guides/silent-mode[Silent Mode] and the database requires upgrading. Silent Mode is an optional runtime mode of FusionAuth that can automatically handle upgrades on startup. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. Learn more about the different runtime modes and how they affect database upgrades in the link:/#FAQs[FAQs] section below.
 
 === Connected Applications and Client Libraries
 
@@ -309,8 +309,6 @@ In the context of a FusionAuth upgrade rollback, the RPO would be the time since
 The RPO effectively measures the maximum tolerable data loss in the event of a rollback, and the RTO measures the time it takes to recover from the failure.
 
 
-
-
 == FAQs
 
 include::docs/v1/tech/installation-guide/_modes.adoc[]

From 0029d16ba7d49d7ebfcd7b266c86f36c1e0e18b6 Mon Sep 17 00:00:00 2001
From: worktheclock <85885287+worktheclock@users.noreply.github.com>
Date: Thu, 10 Aug 2023 16:45:11 +0200
Subject: [PATCH 38/55] Updated upgrade guide language edit

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 28 ++++++++++++----------
 1 file changed, 15 insertions(+), 13 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 5e5926924c..d1d9b1faaa 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -29,7 +29,7 @@ Topics covered in this document:
 ** <<Rolling Upgrade>>
 ** <<Blue-Green Deployment>>
 ** <<Out-of-Band Database Upgrades>>
-* <<FAQs>>
+* <<FAQ>>
 * <<Detailed Upgrade Instructions>>
 ** <<Docker>>
 ** <<Homebrew>>
@@ -94,7 +94,7 @@ If you want to run the migrations interactively, you can run any needed scripts
 You should always back up your database before upgrading. Doing so gives you the ability to roll back.
 ====
 
-The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for link:/docs/v1/tech/guides/silent-mode[Silent Mode] and the database requires upgrading. Silent Mode is an optional runtime mode of FusionAuth that can automatically handle upgrades on startup. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. Learn more about the different runtime modes and how they affect database upgrades in the link:/#FAQs[FAQs] section below.
+The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for link:/docs/v1/tech/guides/silent-mode[Silent Mode] and the database requires upgrading. Silent Mode is an optional runtime mode that can automatically handle upgrades on startup. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. Learn more about the different runtime modes and how they affect database upgrades in the link:/#FAQs[FAQ] section below.
 
 === Connected Applications and Client Libraries
 
@@ -292,24 +292,26 @@ fusionauth-database-schema/
 
 == Rolling Back an Upgrade
 
-In the event that an upgrade is not successful or causes unexpected issues, you may need to rollback your FusionAuth instance to a previous version. Below are the steps for initiating a rollback:
+If your upgrade is unsuccessful or causes unexpected issues, you may need to roll back your FusionAuth instance to a previous version. 
 
-1.  Stop your FusionAuth instances. 
-2.  Initiate the process to restore from the database backup, which you should have taken prior to starting the upgrade.
-3.  Re-deploy FusionAuth but use the previous version you were using instead of the new one. How you do this will depend on your deployment method. 
+Here are the steps for initiating a rollback:
 
-If you are running a FusionAuth Cloud deployment, you can find instructions for rolling back an upgrade here: link:/docs/v1/tech/installation-guide/cloud#rolling-back-from-a-problematic-upgrade[Rolling Back from a Problematic Upgrade].
+1. Stop your FusionAuth instances. 
+2. Initiate the process to restore from the database backup, which you should have taken prior to starting the upgrade.
+3. Redeploy FusionAuth but use the previous version you used instead of the new one. How you do this will depend on your deployment method. 
 
-It's import to consider the timing implications of a rollback, or any disaster recovery process. RTO, or Recovery Time Objective, is the targeted duration of time within which a service should be restored after an outage to avoid unacceptable consequences. Simply put, it is how long you can afford to be without the service or system before it greatly impacts your business. It represents the goal for the time taken to recover from failure.
+If you are running a FusionAuth Cloud deployment, you can find instructions for rolling back an upgrade here: link:/docs/v1/tech/installation-guide/cloud#rolling-back-from-a-problematic-upgrade[Rolling Back From a Problematic Upgrade].
 
-RPO, or Recovery Point Objective, on the other hand, refers to the maximum tolerable amount of data loss measured in time. RPO is determined by looking at the time of the last backup you need to restore from and the restore time. 
+It's important to consider the timing implications of a rollback or any disaster recovery process. RTO, or Recovery Time Objective, is the targeted period time within which a service should be restored after an outage to avoid unacceptable consequences. Simply put, it is how long you can afford to be without the service or system before it severely impacts your business. It represents the goal for the time taken to recover from failure.
 
-In the context of a FusionAuth upgrade rollback, the RPO would be the time since the last backup was taken before the upgrade, and the RTO would be the time it takes to stand up the older version of the system and restore the database. 
+RPO, or Recovery Point Objective, on the other hand, refers to the maximum tolerable amount of data loss measured in time. Determine RPO by looking at the time of the last backup you need to restore from and the restore time. 
+
+In the context of a FusionAuth upgrade rollback, the RPO would be the time since the last backup before the upgrade, and the RTO would be the time it takes to stand up the older version of the system and restore the database. 
 
 The RPO effectively measures the maximum tolerable data loss in the event of a rollback, and the RTO measures the time it takes to recover from the failure.
 
 
-== FAQs
+== FAQ
 
 include::docs/v1/tech/installation-guide/_modes.adoc[]
 
@@ -332,7 +334,7 @@ This section will guide you with detailed technical instructions on how to upgra
 
 === Cloud 
 
-To upgrade your FusionAuth Cloud instance, see link:/docs/v1/tech/installation-guide/cloud#upgrading-a-deployment[Cloud Installation Guide].
+To upgrade your FusionAuth Cloud instance, see the link:/docs/v1/tech/installation-guide/cloud#upgrading-a-deployment[Cloud Installation Guide].
 
 === Docker
 
@@ -345,7 +347,7 @@ include::docs/v1/tech/shared/_upgrade-using-brew.adoc[]
 
 === ZIP Packages
 
-FusionAuth is available in a ZIP package for macOS, Linux, and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth. You can find the ZIP packages at the FusionAuth https://fusionauth.io/download[Downloads] page.
+FusionAuth is available in a ZIP package for macOS, Linux, and Windows. If you are using the ZIP package, please use this guide to update an existing instance of FusionAuth. Find the ZIP packages at the FusionAuth https://fusionauth.io/download[Downloads] page.
 
 ==== macOS and Linux
 

From dc34aee6bd8992168442b4fcced6b21ad960365e Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Wed, 16 Aug 2023 16:10:29 -0600
Subject: [PATCH 39/55] don't need these anymore.

they are done in mermaid now
---
 .../admin-guide/blue_green_upgrade.plantuml   | 22 -------------------
 .../docs/admin-guide/rolling_upgrade.plantuml | 14 ------------
 2 files changed, 36 deletions(-)
 delete mode 100644 site/_diagrams/docs/admin-guide/blue_green_upgrade.plantuml
 delete mode 100644 site/_diagrams/docs/admin-guide/rolling_upgrade.plantuml

diff --git a/site/_diagrams/docs/admin-guide/blue_green_upgrade.plantuml b/site/_diagrams/docs/admin-guide/blue_green_upgrade.plantuml
deleted file mode 100644
index d6c99e7d6b..0000000000
--- a/site/_diagrams/docs/admin-guide/blue_green_upgrade.plantuml
+++ /dev/null
@@ -1,22 +0,0 @@
-@startuml
-  !include ../../_config.plantuml
-
-actor "Users" as u
-agent "Load Balancer" as lb
-
-rectangle "Blue Deployment (old version)" as f1 {
-   [Node 1]#lightblue
-   [Node 2]#lightblue
-   [Node 3]#blue;text:white
-}
-
-rectangle "Green Deployment (new version)" as f2 {
-   [Node #1]#lightgreen
-   [Node #2]#lightgreen
-   [Node #3]#lightgreen
-}
-
-u -> lb
-lb -> f1
-lb ..> f2 : Switch traffic when ready
-@enduml
diff --git a/site/_diagrams/docs/admin-guide/rolling_upgrade.plantuml b/site/_diagrams/docs/admin-guide/rolling_upgrade.plantuml
deleted file mode 100644
index 9fd2d97e1d..0000000000
--- a/site/_diagrams/docs/admin-guide/rolling_upgrade.plantuml
+++ /dev/null
@@ -1,14 +0,0 @@
-@startuml
-  !include ../../_config.plantuml
-
-actor "Users" as u
-agent "Load Balancer" as lb
-component "Node 1" as n1 #lightgreen
-component "Node 2" as n2 #lightblue
-component "Node 3" as n3 #lightblue
-
-u -> lb
-lb ..> n1 : Switch traffic when ready \n (Upgrade one node at a time)
-lb --> n2
-lb -> n3
-@enduml

From 139ee80d7a0aa02edf16bfb609996dcb50c466be Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Wed, 16 Aug 2023 16:27:10 -0600
Subject: [PATCH 40/55] Moved FAQ section around

---
 .../v1/tech/installation-guide/fusionauth-app.adoc     | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/site/docs/v1/tech/installation-guide/fusionauth-app.adoc b/site/docs/v1/tech/installation-guide/fusionauth-app.adoc
index bbcb766f87..48998a3fac 100644
--- a/site/docs/v1/tech/installation-guide/fusionauth-app.adoc
+++ b/site/docs/v1/tech/installation-guide/fusionauth-app.adoc
@@ -17,6 +17,7 @@ bundle provides access to the API and the web based user interface.
 - <<Maintenance Mode>>
 - <<Advanced Installation>>
 - <<Troubleshooting>>
+- <<FAQs>>
 
 == Download the Package
 
@@ -128,11 +129,6 @@ net start FusionAuthApp
 ----
 
 
-== FAQs
-
-include::docs/v1/tech/installation-guide/_modes.adoc[]
-
-
 == Runtime Modes
 
 The runtime mode may be configured to trigger or suppress environment specific runtime behavior.
@@ -345,3 +341,7 @@ the instructions in the <<Start FusionAuth App>> section above.
 
 include::docs/v1/tech/installation-guide/_troubleshooting-runtime-modes-at-startup.adoc[]
 
+== FAQs
+
+include::docs/v1/tech/installation-guide/_modes.adoc[]
+

From d0bccb5278a2d5d22cc87c603214630cd73a1f51 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Wed, 16 Aug 2023 16:28:06 -0600
Subject: [PATCH 41/55] Small fixes

Broke out steps for upgrade to be more clear.
moved faq around
added load balancer note
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 43 +++++++++++++++-------
 1 file changed, 30 insertions(+), 13 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index d1d9b1faaa..756c31784a 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -29,7 +29,7 @@ Topics covered in this document:
 ** <<Rolling Upgrade>>
 ** <<Blue-Green Deployment>>
 ** <<Out-of-Band Database Upgrades>>
-* <<FAQ>>
+* <<Upgrade FAQs>>
 * <<Detailed Upgrade Instructions>>
 ** <<Docker>>
 ** <<Homebrew>>
@@ -151,22 +151,29 @@ If minimizing downtime is a goal, then rolling upgrades or a blue-green deployme
 
 === Rolling Upgrade
 
-You can perform a rolling upgrade if you have three FusionAuth nodes running behind a load balancer. The nodes are upgraded one at a time and the load balancer is configured to direct traffic to the upgraded nodes as they become available for use. This allows you to upgrade FusionAuth with minimal downtime. 
+You can perform a rolling upgrade if you have multiple FusionAuth nodes running behind a load balancer. The nodes are upgraded one at a time and the load balancer is configured to direct traffic to the upgraded nodes as they become available for use. This allows you to upgrade FusionAuth with minimal downtime.
+
+[NOTE]
+====
+This upgrade method requires a load balancer and multiple FusionAuth nodes.
+====
 
 Because individual nodes are taken offline during the rolling update, the capacity of your installation is reduced during the upgrade.
 
 You can choose to run in-place upgrades on each node or to replace each node with a new node running the latest version of FusionAuth. In-place upgrades are simpler and faster because you don't have to spin up a new server, but if something goes wrong, rolling back the upgrade is more complex. Replacing nodes may be slower, but if something goes wrong, you can revert to the previous version of FusionAuth by pointing the load balancer to the old nodes.
 
-An in-place rolling upgrade procedure might look like this:
-
-- Stop the first node and remove it from the load balancer.
-- Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. For core login functionality, they should be minimal.
-- Add the first node back to the load balancer.
-- Stop the second and third nodes, remove them from the load balancer, and upgrade them. 
-- Start the second and third nodes and add them back to the load balancer.
+An in-place rolling upgrade procedure for a three node cluster might look like this:
 
-There is still downtime with this procedure, but it is limited to the time it takes to run the first node to run the database migration. There will be limited capacity during the upgrade while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
+1. Stop the first node and remove it from the load balancer.
+1. Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *For core login functionality, they should be minimal.*
+1. Add the first node back to the load balancer.
+1. Remove the second and third nodes from the load balancer
+1. Stop the second and third nodes.
+1. Upgrade the second and third nodes.
+1. Start the second and third nodes.
+1. Add the second and third nodes back to the load balancer.
 
+There is still downtime with this procedure, but it is limited to the time it takes to run the first node to run the database migration. There will be limited capacity during the upgrade (only the first node) while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
 
 ++++
 {% mermaid %}
@@ -183,7 +190,17 @@ graph TB
 
 A blue-green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue-green deployment instead of performing a rolling upgrade isolates the upgrade process from the production environment, reducing the impact and risk to the current production environment.
 
-To perform a blue-green deployment with a three-node cluster, first create three new nodes with the new version of FusionAuth on each of them. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. The original nodes might give errors as they will not have access to the database. These original nodes can be removed from the load balancer. Add the new nodes to the cluster. 
+[NOTE]
+====
+This upgrade method requires a load balancer and multiple FusionAuth nodes.
+====
+
+To perform a blue-green deployment with a three-node cluster, follow these steps.
+
+1. Create three new nodes with the new version of FusionAuth.
+1. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. Note that there will be a schema mismatch between the new node and the original nodes, so the original nodes may give errors while the new node  is upgrading the database. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *For core login functionality, they should be minimal.*
+1. Add the new nodes to the load balancer.
+1. Remove the old nodes from the load balancer.
 
 With this approach, the system will be down for the duration of the database upgrade but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
 
@@ -311,12 +328,12 @@ In the context of a FusionAuth upgrade rollback, the RPO would be the time since
 The RPO effectively measures the maximum tolerable data loss in the event of a rollback, and the RTO measures the time it takes to recover from the failure.
 
 
-== FAQ
+== Upgrade FAQs
 
 include::docs/v1/tech/installation-guide/_modes.adoc[]
 
 **Q:** How many versions can I skip? +
-**A:** We recommended migrating from one minor version to the next.
+**A:** We recommended migrating from one minor version to the next. Read the release notes carefully and test your upgrade.
 
 **Q:** How often should I upgrade? +
 **A:** You can upgrade whenever you want to. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release: within the last three minor versions. In addition, we don't typically backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix. We recommend you set up a regular cadence of reviewing and upgrading FusionAuth that fits your business needs, the same as you would with a framework or library your application depends on.

From a81c952f63967251278213594745dd9cd221c390 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Wed, 16 Aug 2023 16:42:18 -0600
Subject: [PATCH 42/55] fixing asciidoc warning

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 756c31784a..5af8db61c0 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -165,13 +165,13 @@ You can choose to run in-place upgrades on each node or to replace each node wit
 An in-place rolling upgrade procedure for a three node cluster might look like this:
 
 1. Stop the first node and remove it from the load balancer.
-1. Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *For core login functionality, they should be minimal.*
-1. Add the first node back to the load balancer.
-1. Remove the second and third nodes from the load balancer
-1. Stop the second and third nodes.
-1. Upgrade the second and third nodes.
-1. Start the second and third nodes.
-1. Add the second and third nodes back to the load balancer.
+2. Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *For core login functionality, they should be minimal.*
+3. Add the first node back to the load balancer.
+4. Remove the second and third nodes from the load balancer
+5. Stop the second and third nodes.
+6. Upgrade the second and third nodes.
+7. Start the second and third nodes.
+8. Add the second and third nodes back to the load balancer.
 
 There is still downtime with this procedure, but it is limited to the time it takes to run the first node to run the database migration. There will be limited capacity during the upgrade (only the first node) while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
 
@@ -198,9 +198,9 @@ This upgrade method requires a load balancer and multiple FusionAuth nodes.
 To perform a blue-green deployment with a three-node cluster, follow these steps.
 
 1. Create three new nodes with the new version of FusionAuth.
-1. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. Note that there will be a schema mismatch between the new node and the original nodes, so the original nodes may give errors while the new node  is upgrading the database. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *For core login functionality, they should be minimal.*
-1. Add the new nodes to the load balancer.
-1. Remove the old nodes from the load balancer.
+2. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. Note that there will be a schema mismatch between the new node and the original nodes, so the original nodes may give errors while the new node  is upgrading the database. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *For core login functionality, they should be minimal.*
+3. Add the new nodes to the load balancer.
+4. Remove the old nodes from the load balancer.
 
 With this approach, the system will be down for the duration of the database upgrade but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
 

From 9bcf459a614a2436df290eee759118c21d9cc629 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 08:24:44 -0600
Subject: [PATCH 43/55] More notes about the out of band option

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 5af8db61c0..93072d026c 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -83,7 +83,7 @@ Plan for any downtime or maintenance windows required for the upgrade. If change
 
 FusionAuth can perform database migrations automatically and silently using a process called link:/docs/v1/tech/guides/silent-mode[Silent Mode]. 
 
-If you want to run the migrations interactively, you can run any needed scripts out of band (meaning directly on the database yourself). The general process would be to: 
+If you want to run the database migrations interactively or with other tooling, you can run any needed scripts out of band (meaning directly on the database yourself). The general process would be to: 
 
 - Remove all server nodes from a load balancer/proxy.
 - Run the database migration scripts.
@@ -143,12 +143,14 @@ You should always back up your database before upgrading regardless of the upgra
 
 === Easiest Route
 
-The easiest upgrade route is to simply stop all your services, upgrade each FusionAuth instance, and then bring it all back online. 
+The easiest upgrade route is to simply stop all your services, upgrade each FusionAuth node, and then bring it all back online. In this case, FusionAuth will be performing the database upgrade, if needed, while the servers are stopped.
 
 This is a good option for single-instance development or QA systems, or for systems that can tolerate longer periods of downtime. For instance, if you know you have near-zero user activity at midnight, you can upgrade then. If you have scheduled downtime for other components of your system, that is a good time to upgrade FusionAuth in this manner.
 
 If minimizing downtime is a goal, then rolling upgrades or a blue-green deployment might be more suitable. 
 
+You can also stop all nodes and run the database migration SQL statements yourself, rather than relying on FusionAuth to run them. See <<Downtime and Database Migrations>> for more.
+
 === Rolling Upgrade
 
 You can perform a rolling upgrade if you have multiple FusionAuth nodes running behind a load balancer. The nodes are upgraded one at a time and the load balancer is configured to direct traffic to the upgraded nodes as they become available for use. This allows you to upgrade FusionAuth with minimal downtime.

From b303a3479195f7f1d0065bcd5d4008c67727b53b Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:15:07 -0600
Subject: [PATCH 44/55] Apply suggestions from code review

wordsmithing.

Co-authored-by: Spencer Witt <spencer@fusionauth.io>
---
 site/docs/v1/tech/installation-guide/_modes.adoc     |  2 +-
 .../v1/tech/installation-guide/_theme-upgrade.adoc   | 12 ++++++------
 site/docs/v1/tech/shared/_upgrade-using-docker.adoc  |  2 +-
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/site/docs/v1/tech/installation-guide/_modes.adoc b/site/docs/v1/tech/installation-guide/_modes.adoc
index a61427babe..4413738192 100644
--- a/site/docs/v1/tech/installation-guide/_modes.adoc
+++ b/site/docs/v1/tech/installation-guide/_modes.adoc
@@ -5,4 +5,4 @@
 **A:** Maintenance Mode is a special admin interface for FusionAuth installations in development environments. Maintenance Mode helps you to interactively upgrade FusionAuth or set up database connections. You can switch to Maintenance Mode by switching to the `development` runtime mode and setting Silent Mode to false. Note that Maintenance Mode should never be used in production.
 
 **Q:** What is Silent Mode? +
-**A:** link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments. Silent Mode can be enabled in the `development` runtime mode and as of version `1.19.0`, in the `production` runtime mode too. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will display an error message on the login page. You should always test your database migrations in a non-production or staging environment before deploying to production.
\ No newline at end of file
+**A:** link:/docs/v1/tech/guides/silent-mode[Silent Mode] is a feature of FusionAuth that automatically applies database migrations. This is useful for automated deployments. Silent Mode can be enabled in the `development` runtime mode and, as of version `1.19.0`, in the `production` runtime mode too. Silent Mode will attempt to perform database migrations on startup. If the database migrations fail, FusionAuth will display an error message on the login page. You should always test your database migrations in a non-production or staging environment before deploying to production.
\ No newline at end of file
diff --git a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
index 500e48b2b4..08238e8c39 100644
--- a/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
+++ b/site/docs/v1/tech/installation-guide/_theme-upgrade.adoc
@@ -1,8 +1,8 @@
 === Templates
 
-When new functionality is introduced to link:/docs/v1/tech/core-concepts/integration-points#hosted-login-pages[the hosted login pages], new theme templates are occasionally added. They are added to the default theme by the upgrade process but if you've customized your theme to fit your brand, you'll need to modify the theme to have the new template.
+When new functionality is introduced to link:/docs/v1/tech/core-concepts/integration-points#hosted-login-pages[the hosted login pages], new theme templates are occasionally added. They are added to the default theme by the upgrade process, but if you've customized your theme to fit your brand, you'll need to modify the theme to have the new template.
 
-In the version release notes, any new templates and macros are documented. If there are changes, you'll want to take a closer look at the themes post upgrade.
+New templates and macros are documented in the release notes. If there are additions to a theme, you'll want to take a closer look at the themes after the upgrade.
 
 As part of your upgrade testing, open the administrative user interface and navigate to [breadcrumb]#Customizations > Themes#.
 
@@ -19,11 +19,11 @@ You can use the https://github.com/FusionAuth/fusionauth-theme-helper[Theme Help
 
 ==== Using the Theme Helper to Upgrade Themes
 
-Clone the https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] repo and follow the install instructions in the `README.md` file. 
+Clone the https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper repo] and follow the install instructions in the `README.md` file. 
 
 Download the base themes from your existing version of FusionAuth and the new version of FusionAuth to compare.
 
-To get the existing version's theme files, create a `.env` file from the `.env.sample` file. Create an link:/docs/v1/tech/apis/authentication#managing-api-keys[API key] with read permissions for Themes in the FusionAuth administrative user interface. Add the API key to the `.env` file. The FusionAuth link:/docs/v1/tech/reference/limitations#default-configuration[default theme has the same ID `75a068fd-e94b-451a-9aeb-3ddb9a3b5987`] across all instances. Use this value to update the `THEME_ID` key in the `.env` file.
+To get the existing version's theme files, create a `.env` file from the `.env.sample` file. Use the FusionAuth administrative user interface to create an link:/docs/v1/tech/apis/authentication#managing-api-keys[API key] with read permissions for Themes. Add the API key to the `.env` file. The link:/docs/v1/tech/reference/limitations#default-configuration[default theme] uses the ID `75a068fd-e94b-451a-9aeb-3ddb9a3b5987` across all instances. Use this value to update the `THEME_ID` key in the `.env` file.
 
 In the `.env` file, set the `FUSIONAUTH_URL` to the URL of your existing FusionAuth instance. Finally, update the `TMP_DIR` to a directory on your local machine where you want the existing theme files to be downloaded, such as `current-theme`.
 
@@ -33,7 +33,7 @@ Once the download is complete, you'll need to get the base theme files from the
 
 Once you've got the new version of FusionAuth running, you can update the Theme Helper `.env` file in the Theme Helper repo to point to the new version of FusionAuth. If running locally, update the `FUSIONAUTH_URL` to `\http://localhost:9011`. 
 
-Log in to the new version of FusionAuth to create an API key and copy the link:/docs/v1/tech/reference/limitations#default-configuration[default theme ID `75a068fd-e94b-451a-9aeb-3ddb9a3b5987`] into the `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
+Log in to the new version of FusionAuth to create an API key and use the same link:/docs/v1/tech/reference/limitations#default-configuration[default theme] ID `75a068fd-e94b-451a-9aeb-3ddb9a3b5987` for the `THEME_ID` variable as you did for the existing version. Finally, update the `TMP_DIR` to a directory on your local machine where you want the new theme files to be downloaded, such as `new-theme`. Make sure it is a different directory than the one you used for the existing theme files.
 
 Now you can run the `download.sh` script again to download the new theme files to the `TMP_DIR` directory.
 
@@ -42,7 +42,7 @@ Once you have both sets of theme files downloaded, you can run the `diff-themes.
 ```sh
 ./diff-themes.sh current-theme new-theme
 ```
-The script will output a list of files that show differences between the two sets of theme files and the differences. You can use this list to update your customized theme files. While you can directly use this output to find the changes, it might be useful to use a visual diff tool to help you make the changes, using the file list as a guide.
+The script will output a list of files with differences between the two themes along with the detailed diff for each file. You can use this output to update your customized theme files or use the file list as a guide along with an external diff tool.
 
 === Messages
 
diff --git a/site/docs/v1/tech/shared/_upgrade-using-docker.adoc b/site/docs/v1/tech/shared/_upgrade-using-docker.adoc
index 04bcec9663..de64204786 100644
--- a/site/docs/v1/tech/shared/_upgrade-using-docker.adoc
+++ b/site/docs/v1/tech/shared/_upgrade-using-docker.adoc
@@ -3,4 +3,4 @@ To upgrade FusionAuth when running with `docker-compose`:
 . Stop the instance: `docker-compose down`.
 . Modify the `docker-compose.yml` file to point to the version of FusionAuth you want. You can see https://hub.docker.com/r/fusionauth/fusionauth-app[available tags].
 . Start it up: `docker-compose up`.
-. Login to the administrative UI.
\ No newline at end of file
+. Log in to the administrative UI.
\ No newline at end of file

From 3f7cbbefcde8bfea0495dd41f9866661a9e34e46 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:15:47 -0600
Subject: [PATCH 45/55] wordsmithing

Co-authored-by: Spencer Witt <spencer@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 93072d026c..aeb018feb6 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -338,7 +338,7 @@ include::docs/v1/tech/installation-guide/_modes.adoc[]
 **A:** We recommended migrating from one minor version to the next. Read the release notes carefully and test your upgrade.
 
 **Q:** How often should I upgrade? +
-**A:** You can upgrade whenever you want to. It is your dependency and we won't force you. We do recommend staying relatively close to the latest release: within the last three minor versions. In addition, we don't typically backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix. We recommend you set up a regular cadence of reviewing and upgrading FusionAuth that fits your business needs, the same as you would with a framework or library your application depends on.
+**A:** We recommend staying within the last three minor versions, but we will not force an upgrade. In addition, we typically don't backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix. We recommend you set up a regular cadence of reviewing and upgrading FusionAuth that fits your business needs, the same as you would with a framework or library your application depends on.
 
 
 **Q:** How can I find out about new releases? +

From e3dc212143160242376ed0536f7d41d7a9b6cdb5 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:16:04 -0600
Subject: [PATCH 46/55] better link text.

Co-authored-by: Spencer Witt <spencer@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index aeb018feb6..373edea6b5 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -342,7 +342,7 @@ include::docs/v1/tech/installation-guide/_modes.adoc[]
 
 
 **Q:** How can I find out about new releases? +
-**A:** We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. There are a link:/docs/v1/tech/admin-guide/releases[variety of ways to be notified of releases, including an email list and RSS feed].
+**A:** We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. There are a variety of ways to be link:/docs/v1/tech/admin-guide#release-notifications/releases[notified of releases], including an email list and RSS feed.
 
 **Q:** Does FusionAuth support zero-downtime upgrades? +
 **A:** At this time, it does not when there is a database change. While there are a variety of options that can minimize downtime, upgrades will cause downtime whenever a schema change is required. Please https://github.com/FusionAuth/fusionauth-issues/issues/1240[review and upvote this issue] if zero-downtime upgrades are important to you.

From b2b706f4358bc0e80562a35a54ee3a848e43dae4 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:16:24 -0600
Subject: [PATCH 47/55] clarify zero downtime upgrade situation

Co-authored-by: Spencer Witt <spencer@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 373edea6b5..ac8e1bf16f 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -345,7 +345,7 @@ include::docs/v1/tech/installation-guide/_modes.adoc[]
 **A:** We publish release notes for every release. You can find them here: link:/docs/v1/tech/release-notes[Release Notes]. There are a variety of ways to be link:/docs/v1/tech/admin-guide#release-notifications/releases[notified of releases], including an email list and RSS feed.
 
 **Q:** Does FusionAuth support zero-downtime upgrades? +
-**A:** At this time, it does not when there is a database change. While there are a variety of options that can minimize downtime, upgrades will cause downtime whenever a schema change is required. Please https://github.com/FusionAuth/fusionauth-issues/issues/1240[review and upvote this issue] if zero-downtime upgrades are important to you.
+**A:** At this time, FusionAuth does not support zero-downtime upgrades when there is a database change. While there are a variety of options that can minimize downtime, upgrades will cause downtime whenever a schema change is required. Please https://github.com/FusionAuth/fusionauth-issues/issues/1240[review and upvote this issue] if zero-downtime upgrades are important to you.
 
 == Detailed Upgrade Instructions
 

From 964c4412ec2b2b8d862a1d22f41919c12763c139 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:23:58 -0600
Subject: [PATCH 48/55] Apply suggestions from code review

Lots of good feedback and suggestions from Spencer.

Co-authored-by: Spencer Witt <spencer@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 73 ++++++++++++----------
 1 file changed, 40 insertions(+), 33 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index ac8e1bf16f..8d26af672b 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -8,7 +8,7 @@ navcategory: admin
 
 == Upgrading
 
-If you're considering upgrading FusionAuth to a later version, this document will help you understand the upgrade process and how to plan for it. It also covers detailed instructions on how to upgrade FusionAuth on various platforms and distributions.
+If you're considering upgrading FusionAuth, this document will help you understand the upgrade process and how to plan for it. It also covers detailed instructions on how to upgrade FusionAuth on various platforms and distributions.
 
 Topics covered in this document:
 
@@ -59,9 +59,9 @@ You might want to delay upgrading in the following situations:
 
 You can stay informed about new FusionAuth releases and updates by:
 
-* Signing up for link:/docs/v1/tech/admin-guide/releases[release notifications].
+* Signing up for link:/docs/v1/tech/admin-guide/releases#release-notifications[release notifications].
 * Monitoring the link:/docs/v1/tech/release-notes[release notes].
-* Joining the https://fusionauth.io/community[FusionAuth community] forum and/or slack.
+* Joining the https://fusionauth.io/community[FusionAuth community] forum and/or Slack.
 * Following FusionAuth on social media platforms, including https://twitter.com/FusionAuth[Twitter] and https://www.linkedin.com/company/fusionauth[LinkedIn].
 * Monitoring the https://github.com/FusionAuth/fusionauth-issues/issues[FusionAuth Issues GitHub repository].
 
@@ -75,11 +75,11 @@ Read the link:/docs/v1/tech/release-notes[release notes]. Release notes help you
 
 === Testing
 
-Before starting the upgrade process on production, test the upgrade in a staging or development environment to identify potential issues. This is particularly important on more complex upgrades involving multiple version jumps or if you have made customizations to FusionAuth.
+Before starting the upgrade process on production, test the upgrade in a staging or development environment to identify potential issues. This is particularly important for upgrades involving multiple version jumps or a FusionAuth instance that has been heavily customized.
 
 === Downtime and Database Migrations
 
-Plan for any downtime or maintenance windows required for the upgrade. If changes to the database schema are required, this could require more steps and downtime that affects end users. Such changes are always noted in the release notes. (Read the release notes carefully.) An upgrade without a schema change, on the other hand, may not require any downtime from an end-user perspective.
+Plan for any downtime or maintenance windows required for the upgrade. If changes to the database schema are required, required data migrations could lead to downtime that affects end users. Such changes are always noted in the release notes. (Read the release notes carefully.) An upgrade without a schema change, on the other hand, may not require any downtime from an end-user perspective.
 
 FusionAuth can perform database migrations automatically and silently using a process called link:/docs/v1/tech/guides/silent-mode[Silent Mode]. 
 
@@ -94,7 +94,7 @@ If you want to run the database migrations interactively or with other tooling,
 You should always back up your database before upgrading. Doing so gives you the ability to roll back.
 ====
 
-The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for link:/docs/v1/tech/guides/silent-mode[Silent Mode] and the database requires upgrading. Silent Mode is an optional runtime mode that can automatically handle upgrades on startup. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. Learn more about the different runtime modes and how they affect database upgrades in the link:/#FAQs[FAQ] section below.
+The timing of the database upgrade is also important to note. When an upgraded node is started and connects to the database, it will lock the database immediately if configured for link:/docs/v1/tech/guides/silent-mode[Silent Mode] and the database requires upgrading. Silent Mode is an optional runtime mode that can automatically handle upgrades on startup. This means that the database will be unavailable to other nodes in the cluster until the upgrade is complete. Learn more about the different runtime modes and how they affect database upgrades in the <<Upgrade FAQs>> section below.
 
 === Connected Applications and Client Libraries
 
@@ -102,15 +102,15 @@ Consider that a FusionAuth server upgrade might mean that you need to upgrade yo
 
 In general, client libraries are forward-compatible, but any issues will be noted in the release notes. (Read the release notes carefully.)
 
-If you are using an OIDC compatible library in your application to log your users in, it is unlikely that this integration would require modification. But test it out to make sure.
+If you are using an OIDC compatible library in your application to log your users in, it is unlikely that this integration would require modification, but test it in a non-production environment to make sure.
 
 === Skipping Versions 
 
-Sometimes, you will want to upgrade to a FusionAuth version that is a few versions newer than your current version. For example, you might want to upgrade from version 1.43.0 to 1.45.0. This is called a "version jump". Version jumps include minor versions. FusionAuth can run all the necessary database migrations to get you to the latest version, or you can apply the database migrations yourself.
+Sometimes, you will want to upgrade to a FusionAuth version that is multiple minor versions ahead of your current version. For example, you might want to upgrade from version 1.43.0 to 1.45.0. This is called a "version jump." FusionAuth can run all the necessary database migrations to get you to the latest version, or you can apply the database migrations yourself.
 
-In some cases, version jumps are safe to do. To determine if you can perform a version jump, you should review the link:/docs/v1/tech/release-notes[release notes] carefully. If the releases focus on bug fixes and minor improvements, you can probably perform a version jump safely. Version jumping across patch versions, from 1.43.0 to 1.43.3, for example, is usually safe. Additionally, if the only changes are to features that you are not using, a version jump will work.
+To determine if you can perform a version jump, you should review the link:/docs/v1/tech/release-notes[release notes] carefully. If the releases focus on bug fixes and minor improvements, you can probably perform a version jump safely. Version jumping across patch versions, for example from 1.43.0 to 1.43.3, is usually safe.
 
-The alternative to a version jump is to migrate and test at each version of FusionAuth. For example, if you were moving from 1.43.0 to 1.45.0, you'd upgrade to 1.43.1 and test, then 1.43.2 and test, then 1.43.3 and test, then 1.44.0 and test, then 1.45.0 and test. This is a good option because if there are any issues, you'll be able to know precisely which version of FusionAuth is problematic. It's a great option if you have automated tests that can exercise FusionAuth integrations.
+The alternative to a version jump is to migrate and test at each version of FusionAuth. This is a good option because if there are any issues, you'll be able to know precisely which version of FusionAuth is problematic. It's a great option if you have automated tests that can exercise FusionAuth integrations.
 
 
 Whichever approach you take, you should always test the upgrade in a staging environment to identify potential issues. This is particularly important on more complex upgrades where you are moving between distant minor versions (from 1.22.0 to 1.43.0, for example) or if you have made customizations to FusionAuth. We recommend that the staging environment be as close as possible to your production environment. This includes using the same data, or at least the same data volume, as production. This enables you to test both functionality changes and data update performance times before committing to the upgrade on production.
@@ -149,11 +149,11 @@ This is a good option for single-instance development or QA systems, or for syst
 
 If minimizing downtime is a goal, then rolling upgrades or a blue-green deployment might be more suitable. 
 
-You can also stop all nodes and run the database migration SQL statements yourself, rather than relying on FusionAuth to run them. See <<Downtime and Database Migrations>> for more.
+You can also stop all nodes and run the database migration SQL statements yourself rather than relying on FusionAuth to run them. See <<Downtime and Database Migrations>> for more.
 
 === Rolling Upgrade
 
-You can perform a rolling upgrade if you have multiple FusionAuth nodes running behind a load balancer. The nodes are upgraded one at a time and the load balancer is configured to direct traffic to the upgraded nodes as they become available for use. This allows you to upgrade FusionAuth with minimal downtime.
+You can perform a rolling upgrade if you have multiple FusionAuth nodes running behind a load balancer. The nodes are upgraded one at a time, and the load balancer is configured to direct traffic to the upgraded nodes as they become available for use. This allows you to upgrade FusionAuth with minimal downtime.
 
 [NOTE]
 ====
@@ -167,15 +167,19 @@ You can choose to run in-place upgrades on each node or to replace each node wit
 An in-place rolling upgrade procedure for a three node cluster might look like this:
 
 1. Stop the first node and remove it from the load balancer.
-2. Upgrade FusionAuth on the first node. Once FusionAuth is updated, start it up so that it can perform the database migrations. FusionAuth will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *For core login functionality, they should be minimal.*
-3. Add the first node back to the load balancer.
-4. Remove the second and third nodes from the load balancer
-5. Stop the second and third nodes.
-6. Upgrade the second and third nodes.
-7. Start the second and third nodes.
-8. Add the second and third nodes back to the load balancer.
+2. Upgrade FusionAuth on the first node.
+3. Start FusionAuth on the upgraded node.
+4. The upgraded node will perform required database migrations.*
+5. Add the first node back to the load balancer.
+6. Remove the second and third nodes from the load balancer
+7. Stop the second and third nodes.
+8. Upgrade the second and third nodes.
+9. Start the second and third nodes.
+10. Add the second and third nodes back to the load balancer.
 
-There is still downtime with this procedure, but it is limited to the time it takes to run the first node to run the database migration. There will be limited capacity during the upgrade (only the first node) while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
+* The FusionAuth instance on the upgraded node will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *Errors should be minimal for core login functionality.*
+
+Downtime for this upgrade method is limited to the time it takes the first node to run the database migration. There will be limited capacity while the second and third nodes are upgrading, but the system will be available for use for most of the upgrade process.
 
 ++++
 {% mermaid %}
@@ -190,21 +194,24 @@ graph TB
 
 === Blue-Green Deployment
 
-A blue-green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue-green deployment instead of performing a rolling upgrade isolates the upgrade process from the production environment, reducing the impact and risk to the current production environment.
+A blue-green deployment is a technique that reduces downtime and risk by running two identical environments in parallel. A load balancer is used to direct traffic to one of the environments. Using a blue-green deployment isolates the upgrade process from the existing production servers, reducing the impact and risk compared to a rolling upgrade.
 
 [NOTE]
 ====
 This upgrade method requires a load balancer and multiple FusionAuth nodes.
 ====
 
-To perform a blue-green deployment with a three-node cluster, follow these steps.
+To perform a blue-green deployment with a three node cluster, follow these steps.
 
 1. Create three new nodes with the new version of FusionAuth.
-2. Start up one of the new nodes. When the new node starts and connects to the database, it will lock the database and own it while it completes the database upgrade. Note that there will be a schema mismatch between the new node and the original nodes, so the original nodes may give errors while the new node  is upgrading the database. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *For core login functionality, they should be minimal.*
-3. Add the new nodes to the load balancer.
-4. Remove the old nodes from the load balancer.
+2. Start FusionAuth on one of the new nodes.
+3. The new node will perform required database migrations.*
+4. Add the new nodes to the load balancer.
+5. Remove the old nodes from the load balancer.
+
+* The FusionAuth instance on the upgraded node will lock the database and own it while the database upgrade is completed. Note that there will be a schema mismatch between the first node and the other nodes, so the other nodes may give errors while the first node is being upgraded. The nature of these errors depends on the code paths being updated as well as how users interact with the system. *Errors should be minimal for core login functionality.*
 
-With this approach, the system will be down for the duration of the database upgrade but once the database upgrade is complete, the system will be back online with the upgraded version of FusionAuth on the new nodes. 
+Downtime for this upgrade method is limited to the time it takes the first node to run the database migration, and the system will be back online at full capacity with the upgraded version of FusionAuth on the new nodes immediately following the migration. 
 
 
 ++++
@@ -236,7 +243,7 @@ graph TB
 
 FusionAuth can handle database migrations automatically using link:/docs/v1/tech/guides/silent-mode[Silent Mode]. FusionAuth can also handle updates interactively on development environments using link:/docs/v1/tech/installation-guide/fusionauth-app#maintenance-mode[Maintenance Mode].
 
-In production, you may want to perform the database upgrade rather than allow FusionAuth to do so. This is also known as an out-of-band upgrade. This is useful if you want to perform the database upgrade in a way that minimizes downtime or as part of a larger automated or coordinated deployment. Upgrading the database involves running SQL scripts to update the database schema. 
+In production you may want to perform the database migration yourself rather than allow FusionAuth to do so. This is also known as an out-of-band upgrade. This is useful if you want to perform the database migration in a way that minimizes downtime or as part of a larger automated or coordinated upgrade process. Performing the database migration involves running SQL scripts to update the database schema. 
 
 Depending on your current version and the new version you will be updating to, you might need to execute one or more SQL scripts to update your database. These scripts are located in the migrations folder in the Database Schema ZIP file, which you can download from the link:/direct-download[Direct Downloads] page.
 
@@ -246,7 +253,7 @@ When upgrading your database from a previous version, be sure to only run the sc
  `mysql.sql` and `postgresql.sql` should only be used during a clean installation when no database schema is present.
 ====
 
-Find the FusionAuth migrations in the Database Schema ZIP file. Run them in order, starting with the first migration greater than the version you are coming from, and ending with the version that is less than or equal to the target upgrade version.
+Find the FusionAuth migrations in the Database Schema ZIP file. Run them in order, starting with the first migration greater than your current FusionAuth version, and ending with the version that is less than or equal to the target upgrade version.
 
 For example, if upgrading from version `1.19.1` to `1.22.0`, run the following SQL migrations in this order:
 
@@ -316,8 +323,8 @@ If your upgrade is unsuccessful or causes unexpected issues, you may need to rol
 Here are the steps for initiating a rollback:
 
 1. Stop your FusionAuth instances. 
-2. Initiate the process to restore from the database backup, which you should have taken prior to starting the upgrade.
-3. Redeploy FusionAuth but use the previous version you used instead of the new one. How you do this will depend on your deployment method. 
+2. Initiate the process to restore from the database backup taken prior to starting the upgrade.
+3. Redeploy FusionAuth using your previous version. How you do this will depend on your deployment method. 
 
 If you are running a FusionAuth Cloud deployment, you can find instructions for rolling back an upgrade here: link:/docs/v1/tech/installation-guide/cloud#rolling-back-from-a-problematic-upgrade[Rolling Back From a Problematic Upgrade].
 
@@ -335,7 +342,7 @@ The RPO effectively measures the maximum tolerable data loss in the event of a r
 include::docs/v1/tech/installation-guide/_modes.adoc[]
 
 **Q:** How many versions can I skip? +
-**A:** We recommended migrating from one minor version to the next. Read the release notes carefully and test your upgrade.
+**A:** We recommended migrating from one minor version to the next. Read the release notes carefully and test your upgrade in a non-production environment.
 
 **Q:** How often should I upgrade? +
 **A:** We recommend staying within the last three minor versions, but we will not force an upgrade. In addition, we typically don't backport bug fixes. If you run into an issue with a bug, you'll need to upgrade to get the fix. We recommend you set up a regular cadence of reviewing and upgrading FusionAuth that fits your business needs, the same as you would with a framework or library your application depends on.
@@ -479,7 +486,7 @@ During an upgrade, most everything is saved in the database, so it is safe to de
 \fusionauth\logs
 ----
 
-Extract the new ZIP files and place them in `FUSIONAUTH_HOME`. You may do this using Windows File Explorer or other command line tools to unpack the ZIP archive. In this next step, ensure you delete or move the existing directories to prevent unzipping the new version on top of the existing version. If the new version is unzipped on top of the existing version, you will end up with duplicate libraries in the classpath that will lead to runtime errors.
+Extract the new ZIP files and place them in `FUSIONAUTH_HOME`. You may do this using Windows File Explorer or other command line tools to unpack the ZIP archive. Ensure you delete or move the existing directories to prevent unzipping the new version on top of the existing version. If the new version is unzipped on top of the existing version, you will end up with duplicate libraries in the classpath that will lead to runtime errors.
 
 After you have extracted the new packages, reinstall the Windows services and start them.
 
@@ -548,5 +555,5 @@ include::docs/v1/tech/shared/_troubleshooting-uninstall-upgrade-reinstall-rpm.ad
 
 While FastPath is an option to perform an upgrade, the FastPath process limits the flexibility of the installation in order to get it up and running quickly. We therefore don't recommend you use FastPath install scripts in a production environment.
 
-On Linux in a production environment, use `.deb` or `.rpm` packages. If your production platform is macOS or Windows, please manually manage the upgrade using the `.zip` bundles.
+We recommend using `.deb` or `.rpm` packages on Linux production environments. If your production platform is macOS or Windows, please manually manage the upgrade using the `.zip` bundles.
 

From 13c0bf222c753eddf10ab6805e920d47d9728203 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:35:58 -0600
Subject: [PATCH 49/55] reworking some text based on PR feedback

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 26 ++++++++++++----------
 1 file changed, 14 insertions(+), 12 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 93072d026c..ed2c2221a5 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -112,24 +112,24 @@ In some cases, version jumps are safe to do. To determine if you can perform a v
 
 The alternative to a version jump is to migrate and test at each version of FusionAuth. For example, if you were moving from 1.43.0 to 1.45.0, you'd upgrade to 1.43.1 and test, then 1.43.2 and test, then 1.43.3 and test, then 1.44.0 and test, then 1.45.0 and test. This is a good option because if there are any issues, you'll be able to know precisely which version of FusionAuth is problematic. It's a great option if you have automated tests that can exercise FusionAuth integrations.
 
-
 Whichever approach you take, you should always test the upgrade in a staging environment to identify potential issues. This is particularly important on more complex upgrades where you are moving between distant minor versions (from 1.22.0 to 1.43.0, for example) or if you have made customizations to FusionAuth. We recommend that the staging environment be as close as possible to your production environment. This includes using the same data, or at least the same data volume, as production. This enables you to test both functionality changes and data update performance times before committing to the upgrade on production.
 
-=== Migrating Configuration Between Environments
+=== Updating Configuration 
+
+You'll need to verify if the new version has any new configuration options with defaults that affect your installation. This can be ascertained by reviewing the release notes.
 
-There are a number of options for managing the configuration of your FusionAuth instance over time and promoting changes from one environment to another. These include:
+There are a number of options for managing the configuration of your FusionAuth instance over time and promoting changes from one environment to another. This includes changes from from one version to another.
 
-- Script the changes using a client library.
+Configuration management options include:
+
+- Scripting changes using a client library.
 - Terraform.
 - Pulumi.
 - Manual configuration via the UI.
 
 You can read more in link:/docs/v1/tech/admin-guide/configuration-management[the Configuration Management guide].
 
-=== Themes and Customizations
-
-Review custom themes and how they will be impacted by any FusionAuth updates. If you have made any customizations, you may need to update them to work with the new version of FusionAuth. You can use the https://github.com/FusionAuth/fusionauth-theme-helper[Theme Helper] project to perform diffs on the themes to identify any changes that need to be made.
-
+// this has a hardcoded header
 include::docs/v1/tech/installation-guide/_theme-upgrade.adoc[]
 
 == Upgrade Options
@@ -141,15 +141,17 @@ Maintenance Mode should never be used in production. You don't want your end use
 You should always back up your database before upgrading regardless of the upgrade method you choose.
 ====
 
+For each of the options below, FusionAuth is running any database migrations. However, you can also stop all nodes and run the database migration SQL statements yourself, rather than relying on FusionAuth to run them. See <<Downtime and Database Migrations>> for more.
+
 === Easiest Route
 
-The easiest upgrade route is to simply stop all your services, upgrade each FusionAuth node, and then bring it all back online. In this case, FusionAuth will be performing the database upgrade, if needed, while the servers are stopped.
+The easiest upgrade route is to simply stop all your services, upgrade each FusionAuth node, and then bring it all back online. In this case, FusionAuth will be performing the database upgrade, if needed, when the first node connects to the database.
 
-This is a good option for single-instance development or QA systems, or for systems that can tolerate longer periods of downtime. For instance, if you know you have near-zero user activity at midnight, you can upgrade then. If you have scheduled downtime for other components of your system, that is a good time to upgrade FusionAuth in this manner.
+This is a good option for development instances or non-production systems such as QA.
 
-If minimizing downtime is a goal, then rolling upgrades or a blue-green deployment might be more suitable. 
+This is also a good option for systems that can tolerate longer periods of downtime. For instance, if you know you have near-zero user activity at midnight, you can upgrade then. If you have scheduled downtime for other components of your system, that is a good time to upgrade FusionAuth in this manner.
 
-You can also stop all nodes and run the database migration SQL statements yourself, rather than relying on FusionAuth to run them. See <<Downtime and Database Migrations>> for more.
+If minimizing downtime is a goal, then rolling upgrades or a blue-green deployment might be more suitable. 
 
 === Rolling Upgrade
 

From 3ca0d2e06d9f183736c2f17bf44fbcbd35c65edf Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:45:25 -0600
Subject: [PATCH 50/55] Wordsmithing

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index ed2c2221a5..e4802eddfa 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -22,8 +22,8 @@ Topics covered in this document:
 ** <<Downtime and Database Migrations>>
 ** <<Connected Applications and Client Libraries>>
 ** <<Skipping Versions>>
-** <<Migrating Configuration Between Environments>>
-** <<Themes and Customizations>>
+** <<Updating Configuration>>
+** <<Templates>>
 * <<Upgrade Options>>
 ** <<Easiest Route>>
 ** <<Rolling Upgrade>>
@@ -116,7 +116,7 @@ Whichever approach you take, you should always test the upgrade in a staging env
 
 === Updating Configuration 
 
-You'll need to verify if the new version has any new configuration options with defaults that affect your installation. This can be ascertained by reviewing the release notes.
+Review the release notes to verify if the new version has any new configuration options with defaults that affect your installation.
 
 There are a number of options for managing the configuration of your FusionAuth instance over time and promoting changes from one environment to another. This includes changes from from one version to another.
 

From 492691b0b4beb611deab7d4af7aa635052fb389b Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:46:43 -0600
Subject: [PATCH 51/55] corrected color.

Co-authored-by: Spencer Witt <spencer@fusionauth.io>
---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 8d26af672b..2212bf8d01 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -232,7 +232,7 @@ graph TB
         H(Node 3)
         style F fill:#add8e6
         style G fill:#add8e6
-        style H fill:#C0C0F0
+        style H fill:#add8e6
     end
     B --> |Switch traffic when ready|green
     B --> blue

From d5811ce986057b58e490b77ca0bf27f21d45e00a Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:48:18 -0600
Subject: [PATCH 52/55] remove unneeded header

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 2 --
 1 file changed, 2 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 3741e8808a..573dded2db 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -6,8 +6,6 @@ navcategory: admin
 ---
 :page-liquid:
 
-== Upgrading
-
 If you're considering upgrading FusionAuth, this document will help you understand the upgrade process and how to plan for it. It also covers detailed instructions on how to upgrade FusionAuth on various platforms and distributions.
 
 Topics covered in this document:

From 8e60721ec0920cb76fab0a43dcff24a069e15142 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:52:29 -0600
Subject: [PATCH 53/55] typo/spelling fixes

---
 site/docs/v1/tech/admin-guide/upgrade.adoc                    | 2 +-
 .../_troubleshooting-uninstall-upgrade-reinstall-rpm.adoc     | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 573dded2db..8e0ce65e97 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -116,7 +116,7 @@ Whichever approach you take, you should always test the upgrade in a staging env
 
 Review the release notes to verify if the new version has any new configuration options with defaults that affect your installation.
 
-There are a number of options for managing the configuration of your FusionAuth instance over time and promoting changes from one environment to another. This includes changes from from one version to another.
+There are a number of options for managing the configuration of your FusionAuth instance over time and promoting changes from one environment to another. This includes changes from one version to another.
 
 Configuration management options include:
 
diff --git a/site/docs/v1/tech/shared/_troubleshooting-uninstall-upgrade-reinstall-rpm.adoc b/site/docs/v1/tech/shared/_troubleshooting-uninstall-upgrade-reinstall-rpm.adoc
index 96aded3dee..bad56e86ba 100644
--- a/site/docs/v1/tech/shared/_troubleshooting-uninstall-upgrade-reinstall-rpm.adoc
+++ b/site/docs/v1/tech/shared/_troubleshooting-uninstall-upgrade-reinstall-rpm.adoc
@@ -1,4 +1,4 @@
-Please review the procedure outlined below if attempting perform a clean install or upgrade using RPM's and have experienced a failure that you have been unable to resolve. Please only consider these steps after other attempts have been unsuccessful.
+Please review the procedure outlined below if attempting to perform a clean install or upgrade using RPM's and have experienced a failure that you have been unable to resolve. Please only consider these steps after other attempts have been unsuccessful.
 
 [WARNING]
 ====
@@ -12,7 +12,7 @@ The following steps will produce a clean installation preserving:
 - The FusionAuth config file found in `/usr/local/fusionauth/config/fusionauth.properties`
 - The Elasticsearch index found in `/usr/local/fusionauth/data`
 
-Below assumes both `fusionauth-app` and `fusionauth-search` will be un-installed and re-installed together. If you are not using `fusionauth-search`, you may ignore the steps related to this service.
+Below assumes both `fusionauth-app` and `fusionauth-search` will be uninstalled and reinstalled together. If you are not using `fusionauth-search`, you may ignore the steps related to this service.
 
 === Manual Removal Steps
 

From 1c0ebf32d8a8d1adfc14326780cce94c8390e2a3 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 17:56:12 -0600
Subject: [PATCH 54/55] wordsmithing

---
 site/docs/v1/tech/admin-guide/upgrade.adoc | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 8e0ce65e97..597d005fbb 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -15,7 +15,7 @@ Topics covered in this document:
 ** <<Reasons Not To Upgrade>>
 ** <<Being Aware of Upgrade Options>>
 * <<How to Think About Upgrades>>
-** <<Update Contents and Notes>>
+** <<Version Changes and Notes>>
 ** <<Testing>>
 ** <<Downtime and Database Migrations>>
 ** <<Connected Applications and Client Libraries>>
@@ -67,9 +67,11 @@ You can stay informed about new FusionAuth releases and updates by:
 
 Before upgrading FusionAuth, there are a number of things to consider. Upgrading FusionAuth is similar to upgrading a library your application depends on. Go through each of the points below to see if any of them apply to your situation.
 
-=== Update Contents and Notes
+=== Version Changes and Notes
 
-Read the link:/docs/v1/tech/release-notes[release notes]. Release notes help you understand how an update affects you. They include details on new features, improvements, bug fixes, and potential breaking changes.
+Read the link:/docs/v1/tech/release-notes[release notes]. Release notes help you understand how a version update affects your systems. 
+
+The FusionAuth team strives to provide detailed information for every change in every version, including tying the change back to a GitHub issue. The release notes include details on new features, improvements, workarounds, bug fixes, and potential breaking changes.
 
 === Testing
 
@@ -160,7 +162,7 @@ You can perform a rolling upgrade if you have multiple FusionAuth nodes running
 This upgrade method requires a load balancer and multiple FusionAuth nodes.
 ====
 
-Because individual nodes are taken offline during the rolling update, the capacity of your installation is reduced during the upgrade.
+Because individual nodes are taken offline during the rolling upgrade, the capacity of your installation is reduced during the upgrade.
 
 You can choose to run in-place upgrades on each node or to replace each node with a new node running the latest version of FusionAuth. In-place upgrades are simpler and faster because you don't have to spin up a new server, but if something goes wrong, rolling back the upgrade is more complex. Replacing nodes may be slower, but if something goes wrong, you can revert to the previous version of FusionAuth by pointing the load balancer to the old nodes.
 

From 86c02a4e2a02ff9bdfe5c674ec0d5c755ba6c967 Mon Sep 17 00:00:00 2001
From: Dan Moore <dan@fusionauth.io>
Date: Thu, 17 Aug 2023 18:58:11 -0600
Subject: [PATCH 55/55] put in client library version info into upgrade
 planning

---
 site/docs/v1/tech/admin-guide/upgrade.adoc    |  6 +++-
 .../_client-library-versioning.adoc           | 31 ++++++++++++++++++
 site/docs/v1/tech/client-libraries/index.adoc | 32 +------------------
 3 files changed, 37 insertions(+), 32 deletions(-)
 create mode 100644 site/docs/v1/tech/client-libraries/_client-library-versioning.adoc

diff --git a/site/docs/v1/tech/admin-guide/upgrade.adoc b/site/docs/v1/tech/admin-guide/upgrade.adoc
index 597d005fbb..f7eba88e86 100644
--- a/site/docs/v1/tech/admin-guide/upgrade.adoc
+++ b/site/docs/v1/tech/admin-guide/upgrade.adoc
@@ -98,12 +98,16 @@ The timing of the database upgrade is also important to note. When an upgraded n
 
 === Connected Applications and Client Libraries
 
-Consider that a FusionAuth server upgrade might mean that you need to upgrade your client libraries too. Check if this is needed before upgrading, as it will entail a more complex upgrade process and may require more downtime.
+A FusionAuth upgrade might mean that you need to upgrade your client libraries too. Check if this is needed before upgrading, as it will entail a more complex upgrade process and may require downtime from other components of a your system.
 
 In general, client libraries are forward-compatible, but any issues will be noted in the release notes. (Read the release notes carefully.)
 
 If you are using an OIDC compatible library in your application to log your users in, it is unlikely that this integration would require modification, but test it in a non-production environment to make sure.
 
+==== Client Library Versioning
+
+include::docs/v1/tech/client-libraries/_client-library-versioning.adoc[]
+
 === Skipping Versions 
 
 Sometimes, you will want to upgrade to a FusionAuth version that is multiple minor versions ahead of your current version. For example, you might want to upgrade from version 1.43.0 to 1.45.0. This is called a "version jump." FusionAuth can run all the necessary database migrations to get you to the latest version, or you can apply the database migrations yourself.
diff --git a/site/docs/v1/tech/client-libraries/_client-library-versioning.adoc b/site/docs/v1/tech/client-libraries/_client-library-versioning.adoc
new file mode 100644
index 0000000000..913c22b179
--- /dev/null
+++ b/site/docs/v1/tech/client-libraries/_client-library-versioning.adoc
@@ -0,0 +1,31 @@
+Client library versions track the API. The API will only change with a major or minor version release, not with a patch release.
+
+You should use the version of a client library that corresponds to your version of FusionAuth. If that is not available, use the latest release of the client library for the minor version. 
+
+.Examples of Client Library Versions To Use
+[cols="1,1,3"]
+|===
+| FusionAuth Version | Client Library Version | Notes
+
+| `1.41.0`
+| `1.41.0`
+| Same version
+
+| `1.41.1`
+| `1.41.0`
+| Same minor version
+
+| `1.29.4`
+| `1.29.1`
+| Latest release in the minor version 
+
+| `1.29.1`
+| `1.29.1`
+| Same version
+
+| `1.29.0`
+| `1.29.0`
+| Same version
+
+|===
+
diff --git a/site/docs/v1/tech/client-libraries/index.adoc b/site/docs/v1/tech/client-libraries/index.adoc
index 9bc0feabf1..647291327d 100644
--- a/site/docs/v1/tech/client-libraries/index.adoc
+++ b/site/docs/v1/tech/client-libraries/index.adoc
@@ -71,34 +71,4 @@ include::docs/v1/tech/client-libraries/_how-to-use-client-libraries.adoc[]
 
 == Versioning
 
-Client library versions track the API. The API will only change with a major or minor version release, not with a patch release.
-
-You should use the version of a client library that corresponds to your version of FusionAuth. If that is not available, use the latest release of the client library for the minor version. 
-
-.Examples of Client Library Versions To Use
-[cols="1,1,3"]
-|===
-| FusionAuth Version | Client Library Version | Notes
-
-| `1.41.0`
-| `1.41.0`
-| Same version
-
-| `1.41.1`
-| `1.41.0`
-| Same minor version
-
-| `1.29.4`
-| `1.29.1`
-| Latest release in the minor version 
-
-| `1.29.1`
-| `1.29.1`
-| Same version
-
-| `1.29.0`
-| `1.29.0`
-| Same version
-
-|===
-
+include::docs/v1/tech/client-libraries/_client-library-versioning.adoc[]