From c7f07ec6b1bd192b86150faa16f59602eaa0d5c2 Mon Sep 17 00:00:00 2001
From: Johan Wikman <johan.wikman@mariadb.com>
Date: Wed, 10 Oct 2018 10:39:27 +0300
Subject: [PATCH] Add Upgrading document

---
 .../Upgrading/Upgrading-To-MaxScale-2.3.md    | 39 +++++++++++++++++++
 1 file changed, 39 insertions(+)
 create mode 100644 Documentation/Upgrading/Upgrading-To-MaxScale-2.3.md

diff --git a/Documentation/Upgrading/Upgrading-To-MaxScale-2.3.md b/Documentation/Upgrading/Upgrading-To-MaxScale-2.3.md
new file mode 100644
index 000000000..10ab90fad
--- /dev/null
+++ b/Documentation/Upgrading/Upgrading-To-MaxScale-2.3.md
@@ -0,0 +1,39 @@
+# Upgrading MariaDB MaxScale from 2.2 to 2.3
+
+This document describes possible issues when upgrading MariaDB
+MaxScale from version 2.2 to 2.3.
+
+For more information about MariaDB MaxScale 2.3, please refer
+to the [ChangeLog](../Changelog.md).
+
+Before starting the upgrade, we recommend you back up your current
+configuration file.
+
+### `passwd` is no longer accepted
+
+In the configuration file, passwords for monitors and services must be
+specified using `password`; the support for the earlier deprecated
+`passwd` has been removed. That is, the following
+```
+[The-Service]
+type=service
+passwd=some-service-password
+...
+
+[The-Monitor]
+type=service
+passwd=some-monitor-password
+...
+```
+must be changed to
+```
+[The-Service]
+type=service
+password=some-service-password
+...
+
+[The-Monitor]
+type=service
+password=some-monitor-password
+...
+```