Postgres Operator Upgrade updates (#1051)

* Postgres Operator Upgrade updates

An updated procedure for upgrading the Postgres Operator from
version 4.0.1 to 4.1 is required to account for recent configuration
updates and environmental changes. These changes left certain
Operator features nonfunctional.  The new upgrade procedure
is designed to ensure all applicable changes are accounted for in
the most convenient way possible.

* Updated the PGO 4.0.1 to 4.1.0 procedure to include a missing step
outlining the process to recreate the 4.0.1 clusters in the new
4.1.0 environment.

Also added a reference to the pgo scaledown command's help for use
when needing to scale down the existing PGO 4.0.1 pgclusters.

* Added a separate upgrade procedure for users using the Ansible
installation method for their Operator installation. Procedure is
designed to be inclusive. Other updates reflect renaming of the
existing procedure to specify it is for Bash installations, and
an update to relevant links.

Author: tjmoore4

hugo/content/Upgrade/_index.md

@@ -16,7 +16,9 @@ This section of the documentation shows specific steps required to upgrade diffe
 
 [Upgrade Postgres Operator from 3.5 to 4.1] ( {{< relref "upgrade/upgrade35to4.md" >}})
 
-[Upgrade Postgres Operator from 4.0.1 to 4.1.0] ( {{< relref "upgrade/upgrade40to41.md" >}})
+[Upgrade Postgres Operator from 4.0.1 to 4.1.0 (Bash)] ( {{< relref "upgrade/upgrade40to41_bash.md" >}})
+
+[Upgrade Postgres Operator from 4.0.1 to 4.1.0 (Ansible)] ( {{< relref "upgrade/upgrade40to41_ansible.md" >}})
 
 ## Upgrading A Postgres Cluster
 
@@ -36,4 +38,4 @@ In this example, we are upgrading a cluster from PostgreSQL 11.4 to 11.5 using t
 
 `pgo upgrade mycluster --ccp-image-tag=centos7-11.5-2.4.2`
 
-For more information, please see the `pgo upgrade` documentation [here.] ( {{< relref "operatorcli/cli/pgo_upgrade.md" >}})
+For more information, please see the `pgo upgrade` documentation [here.] ( {{< relref "operatorcli/cli/pgo_upgrade.md" >}})

hugo/content/Upgrade/upgrade35to4.md

@@ -1,13 +1,13 @@
 ---
-title: "Upgrade PGO 3.5 to 4"
-Latest Release: 4.1.0 {docdate}
+title: "Upgrade PGO 3.5 to 4.1"
+Latest Release: 4.1 {docdate}
 draft: false
 weight: 8
 ---
 
-## Upgrading a Cluster from Version 3.5.x to PGO 4
+## Upgrading a Cluster from Version 3.5.x to PGO 4.1
 
-This section will outline the procedure to upgrade a given cluster created using Postgres Operator 3.5.x to PGO version 4.1.
+This section will outline the procedure to upgrade a given cluster created using Postgres Operator 3.5.x to PGO version 4.1
 
 {{% notice info %}}
 

hugo/content/Upgrade/upgrade40to41.md

@@ -0,0 +1,80 @@
+---
+title: "Upgrade PGO 4.0.1 to 4.1.0 (Ansible)"
+Latest Release: 4.1.0 {docdate}
+draft: false
+weight: 8
+---
+
+## Postgres Operator Ansible Upgrade Procedure from 4.0.1 to 4.1.0
+
+This procedure will give instructions on how to upgrade to Postgres Operator 4.1.0 when using the Ansible installation method.
+
+{{% notice info %}}
+
+As with any upgrade, please ensure you have taken recent backups of all relevant data!
+
+{{% / notice %}}
+
+##### Prerequisites.
+You will need the following items to complete the upgrade:
+
+* The latest 4.1.0 code for the Postgres Operator available
+
+These instructions assume you are executing in a terminal window and that your user has admin privileges in your Kubernetes or Openshift environment.
+
+
+##### Step 0
+For the cluster(s) you wish to upgrade, scale down any replicas, if necessary (see `pgo scaledown --help` for more information on command usage) page for more information), then delete the cluster
+
+	pgo delete cluster <clustername>
+
+{{% notice warning %}}
+
+Please note the name of each cluster, the namespace used, and be sure not to delete the associated PVCs or CRDs!
+
+{{% /notice %}}
+
+
+##### Step 1
+
+Save a copy of your current inventory file with a new name (such as `inventory.backup)` and checkout the latest 4.1 tag of the Postgres Operator.
+
+
+##### Step 2
+Update the new inventory file with the appropriate values for your new Operator installation, as described in the [Ansible Install Prerequisites] ( {{< relref "installation/install-with-ansible/prerequisites.md" >}}) and the [Compatibility Requirements Guide] ( {{< relref "configuration/compatibility.md" >}}). 
+
+
+##### Step 3
+
+Now you can upgrade your Operator installation and configure your connection settings as described in the [Ansible Update Page] ( {{< relref "installation/install-with-ansible/updating-operator.md" >}}).
+
+
+##### Step 4
+Verify the Operator is running:
+
+    kubectl get pod -n <operator namespace>
+
+And that it is upgraded to the appropriate version
+
+    pgo version
+
+##### Step 5
+Once the Operator is installed and functional, create new 4.1 clusters with the same name as was used previously. This will allow the new clusters to utilize the existing PVCs.
+
+	pgo create cluster <clustername> -n <namespace>
+
+##### Step 6
+To verify cluster status, run 
+        pgo test <clustername> -n <namespace>
+Output should be similar to:
+```
+psql -p 5432 -h 10.104.74.189 -U postgres postgres is Working
+psql -p 5432 -h 10.104.74.189 -U postgres userdb is Working
+psql -p 5432 -h 10.104.74.189 -U primaryuser postgres is Working
+psql -p 5432 -h 10.104.74.189 -U primaryuser userdb is Working
+psql -p 5432 -h 10.104.74.189 -U testuser postgres is Working
+psql -p 5432 -h 10.104.74.189 -U testuser userdb is Working
+``` 
+##### Step 7
+Scale up to the required number of replicas, as needed.
+