From 5c3abeedc8218243d7bb7ec08d49640dfc6039c6 Mon Sep 17 00:00:00 2001
From: Maciej Zimnoch <maciej@scylladb.com>
Date: Thu, 17 Jun 2021 10:56:11 +0200
Subject: [PATCH] Add upgrade guide for 1.3

---
 docs/source/upgrade.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/docs/source/upgrade.md b/docs/source/upgrade.md
index d8f7b87dea5..4126a2e7dc4 100644
--- a/docs/source/upgrade.md
+++ b/docs/source/upgrade.md
@@ -2,6 +2,24 @@
 
 This pages describes Scylla Operator upgrade procedures.
 
+## `v1.2.0` -> `v1.3.0`
+
+Sidecar image is going to be upgraded automatically, so a rolling restart of your Scylla clusters is expected during the upgrade procedure.
+
+1. Checkout source code of v1.3.0:
+   ```
+   git checkout v1.3.0
+   ```
+1. Update Scylla Operator from deploy directory:
+    ```
+    kubectl -n scylla-operator apply -f deploy/operator
+    ```
+1. Wait until Scylla Operator is up and running:
+    ```
+    kubectl wait --for condition=established crd/scyllaclusters.scylla.scylladb.com
+    kubectl -n scylla-operator rollout status deployment.apps/scylla-operator
+    ```
+
 ## `v1.1.0` -> `v1.2.0`
 
 1.2.0 release brought a lot of changes to the Scylla Operator deployment process.