Update Postgres Operator Upgrade Procedures to Match Updated Code Behavior

In line with commit "Update cluster upgrade"
#1027
The upgrade procedures have been updated.

For the PGO 4.0.1 to 4.1.0 upgrade procedure, the new
functionality is referenced in place of the previous
manner of executing the upgrade.

For the PGO 3.5 Minor Version upgrade procedure, the
upgrade procedure has been updated so that the behavior
will match the updated 4.1.0 code change.

Author: tjmoore4

hugo/content/Upgrade/upgrade35.md

@@ -80,20 +80,41 @@ Verify this by running:
 
 At this point, the Operator should be running the latest minor version of 3.5, and new clusters will be built using the appropriate specifications defined in your pgo.yaml file. For the existing clusters, upgrades can be performed with the following steps.
 
-To bring your clusters up to the latest versions of Containers, for each of your clusters you will want to run the following:
+{{% notice info %}}
+
+Before beginning your upgrade procedure, be sure to consult the [Compatibility Requirements Page]
+( {{< relref "configuration/compatibility.md" >}}) for container dependency information.
+
+{{% / notice %}}
+
+First, update the deployment of each replica, one at a time, with the new image version: 
+
+```
+kubectl edit deployment.apps/yourcluster
 ```
-pgo scaledown <clustername> --query
-pgo scaledown <clustername> --target=<replica-name> --delete-data
+then edit the line containing the image value, which will be similar to the following
+```
+image: crunchydata/crunchy-postgres:centos7-11.3-2.4.0
 ```
-When you scale down the cluster you have the option of passing in the --delete-data flag on the pgo scaledown command. If you do this the pvc bound to your pod will also be deleted. If for some reason you need to keep the pvc around, you can remove this flag.
 
-Now that your cluster only has one pod you can run the minor upgrade:
+When this new deployment is written, it will kill the pod and recreate it with the new image. Do this for each replica, waiting for the previous pod to upgrade completely before moving to next.
 
-    pgo upgrade <clustername>
+Once the replicas have been updated, update the deployment of primary by updating the `image:` line in the same fashion, waiting for it to come back up.
 
-Once the minor upgrade is done you can scale your cluster back to the previous number of replicas:
+Now, similar to the steps above, you will need to update the pgcluster `ccpimagetag:` to the new value:
+```
+kubectl edit pgcluster yourcluster
+```
 
-    pgo scale <clustername> --replica-count=1
+To check everything is now working as expected, execute
+```
+pgo test yourcluster
+```
+To validate the database connections and execute
+```
+pgo show cluster yourcluster
+```
+To check the various cluster elements are listed as expected.
 
 There is a bug in the operator where the image version for the backrest repo deployment is not updated with a pgo upgrade. As a workaround for this you need to redeploy the backrest shared repo deployment with the correct image version.
 

hugo/content/Upgrade/upgrade40to41.md

@@ -163,23 +163,23 @@ Verify this by running:
 
 At this point, the Operator will be running version 4.1.0, and new clusters will be built using the appropriate specifications defined in your pgo.yaml file. For the existing clusters, upgrades can be performed with the following steps.
 
-To bring your clusters up to the latest versions of Postgres and Containers, for each of your clusters you will want to run the following:
-```
-pgo scaledown <clustername> --query
-pgo scaledown <clustername> --target
-```
+{{% notice info %}}
 
-Now that your cluster only has one pod you can run the minor upgrade:
+Before beginning your upgrade procedure, be sure to consult the [Compatibility Requirements Page]
+( {{< relref "configuration/compatibility.md" >}}) for container dependency information.
 
-    pgo upgrade cluster <clustername>
+{{% / notice %}}
 
-By default this command updates the cluster with the values in the pgo.yaml.  If however you are running more than one version of Postgres clusters you can run the following to upgrade any clusters that do not match what is in your current configuration.
+To start, execute the minor upgrade command:
 
-    pgo upgrade <clustername> --ccp-image-tag=<imagetag>
+    pgo upgrade cluster <clustername>
 
-Once the minor upgrade is done you can scale your cluster back to the previous number of replicas, for example:
+If you would like to know more about the Postgres Cluster minor upgrade, please see the [Upgrade Page]
+( {{< relref "upgrade/_index.md" >}}) for additional information.
 
-    pgo scale <clustername> --replica-count=2
+By default this command updates the cluster with the values in the pgo.yaml.  If however you are running more than one version of Postgres clusters you can run the following command to upgrade any clusters that do not match what is in your current configuration.
+
+    pgo upgrade <clustername> --ccp-image-tag=<imagetag>
 
 There is a bug in the operator where the image version for the backrest repo deployment is not updated with a pgo upgrade. As a workaround for this you need to redeploy the backrest shared repo deployment with the correct image version.