Update release doc to include the upgrade test update

This change ensure the upgrade test is working as expected.

Change-Id: I5f6bdbb65a9ea0399da7b828c9994798e51c1e46

Author: TristanCacqueray

docs/developer/release.md

@@ -42,7 +42,8 @@ git tag v0.0.20 HEAD
 git push gerrit v0.0.20
 ```
 
+Once the new release is deployed, update the "sf_operator_stable_version" variable in zuul.d/jobs.yaml.
 
 # Release Automation
 
-The release process is currently manual. This section will be updated once the automation is in place.
+The release process is currently manual. This section will be updated once the automation is in place.

playbooks/minikube-upgrade.yaml

@@ -1,15 +1,8 @@
-# The goal of this playbook is to validate the upgrade to 0.0.63
-# by reproducing a deployment that went from 0.0.60 (before ZK HA) to 0.0.60 (to trigger ZK HA secret issue)
-- name: "Perform upgrade from 0.0.60"
+- name: "Perform upgrade test"
   hosts: controller
   tasks:
-    - name: Deploy version before ZooKeeper HA
-      command: ./hack/deploy-version.sh v0.0.60
-      args:
-        chdir: "{{ zuul.project.src_dir }}"
-
-    - name: Deploy version with incompleted ZooKeeper HA (deploying this one first would work because the secrets would be properly created)
-      command: ./hack/deploy-version.sh v0.0.62
+    - name: Deploy last stable version
+      command: ./hack/deploy-version.sh "{{ sf_operator_stable_version }}"
       args:
         chdir: "{{ zuul.project.src_dir }}"
 

zuul.d/jobs.yaml

@@ -120,3 +120,4 @@
     run: playbooks/minikube-upgrade.yaml
     vars:
       with_loki: false
+      sf_operator_stable_version: v0.0.64