Rewrite and reorganization of the installation section

This accounts for the new `pgo-deployer` container and tries to
present the instructions in an easy to follow way.

Author: Jonathan S. Katz

docs/content/Installation/_index.md

@@ -54,7 +54,7 @@ Delete the 3.5.x version of the operator by executing:
 ##### Step 3
 Log in as your new Linux user and install the 4.3.0 Postgres Operator.
 
-[Bash Installation] ( {{< relref "installation/operator-install.md" >}}) 
+[Bash Installation] ( {{< relref "installation/other/bash.md" >}}) 
 
 Be sure to add the existing namespace to the Operator's list of watched namespaces (see the [Namespace] ( {{< relref "architecture/namespace.md" >}}) section of this document for more information) and make sure to avoid overwriting any existing data storage.
 

docs/content/Installation/common-env.md

@@ -51,12 +51,12 @@ Save a copy of your current inventory file with a new name (such as `inventory.b
 
 
 ##### 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" >}}).
+Update the new inventory file with the appropriate values for your new Operator installation, as described in the [Ansible Install Prerequisites] ( {{< relref "installation/other/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" >}}).
+Now you can upgrade your Operator installation and configure your connection settings as described in the [Ansible Update Page] ( {{< relref "installation/other/ansible/updating-operator.md" >}}).
 
 
 ##### Step 4
@@ -87,6 +87,6 @@ cluster : mycluster
                 primary (mycluster-7d49d98665-7zxzd): UP
 ```
 ##### Step 7
-Scale up to the required number of replicas, as needed. 
+Scale up to the required number of replicas, as needed.
 
 It is also recommended to take full backups of each pgcluster once the upgrade is completed due to version differences between the old and new clusters.

docs/content/Installation/postgres-operator-installer/_index.md

@@ -119,7 +119,7 @@ You will need to edit the `$PGOROOT/deploy/install-bootstrap-creds.sh` file to c
 export PGOADMIN_USERNAME=pgoadmin
 export PGOADMIN_PASSWORD=examplepassword
 ```
-You will need to update the `$HOME/.pgouser`file to match the values you set in order to use the Operator. Additional accounts can be created later following the steps described in the 'Operator Security' section of the main [Bash Installation Guide] ( {{< relref "installation/operator-install.md" >}}). Once these accounts are created, you can change this file to login in via the PGO CLI as that user.
+You will need to update the `$HOME/.pgouser`file to match the values you set in order to use the Operator. Additional accounts can be created later following the steps described in the 'Operator Security' section of the main [Bash Installation Guide] ( {{< relref "installation/other/bash.md" >}}). Once these accounts are created, you can change this file to login in via the PGO CLI as that user.
 
 ##### Step 6
 

docs/content/Installation/prereq/_index.md

@@ -12,7 +12,7 @@ draft: false
 
 Latest Release: 4.3.0
 
-The Crunchy PostgreSQL Operator automates and simplifies deploying and managing open source PostgreSQL clusters on Kubernetes and other Kubernetes-enabled Platforms by providing the essential features you need to keep your PostgreSQL clusters up and running, including:
+The [Crunchy PostgreSQL Operator](https://www.crunchydata.com/developers/download-postgres/containers/postgres-operator) automates and simplifies deploying and managing open source PostgreSQL clusters on Kubernetes and other Kubernetes-enabled Platforms by providing the essential features you need to keep your PostgreSQL clusters up and running, including:
 
 #### PostgreSQL Cluster Provisioning
 
@@ -96,23 +96,21 @@ The Crunchy PostgreSQL Operator extends Kubernetes to provide a higher-level abs
 
 The Crunchy PostgreSQL Operator is tested on the following Platforms:
 
-- Kubernetes 1.13 - 1.15 (See note about 1.16 and beyond)
+- Kubernetes 1.13+
 - OpenShift 3.11+
 - Google Kubernetes Engine (GKE), including Anthos
 - VMware Enterprise PKS 1.3+
 
-**NOTE**: At present, while the Crunchy PostgreSQL Operator has compatibility for Kubernetes 1.16 and beyond, it has not been verified for the v4.3.0 release.
-
 ## Storage
 
 The Crunchy PostgreSQL Operator is tested with a variety of different types of Kubernetes storage and Storage Classes, including:
 
-- Google Compute Engine persistent volumes
-- HostPath
-- NFS
 - Rook
 - StorageOS
+- Google Compute Engine persistent volumes
+- NFS
+- HostPath
 
-and more.
+and more. We have had reports of people using the PostgreSQL Operator with other [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) as well.
 
-We know there are a variety of different types of [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) available for Kubernetes and we do our best to test each one, but due to the breadth of this area we are unable to verify PostgreSQL Operator functionality in each one. With that said, the PostgreSQL Operator is designed to be storage class agnostic and has been demonstrated to work with additional Storage Classes.
+We know there are a variety of different types of [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) available for Kubernetes and we do our best to test each one, but due to the breadth of this area we are unable to verify PostgreSQL Operator functionality in each one. With that said, the PostgreSQL Operator is designed to be storage class agnostic and has been demonstrated to work with additional Storage Classes. Storage is a rapidly evolving field in Kubernetes and we will continue to adapt the PostgreSQL Operator to modern Kubernetes storage standards.

docs/content/Upgrade/upgrade35to4.md

@@ -1,16 +1,17 @@
 ---
-title: "Developer Setup"
+title: "Development Environment"
 date:
 draft: false
 weight: 305
 ---
 
-The [Postgres-Operator](https://github.com/crunchydata/postgres-operator) is an open source project hosted on GitHub.
+The [PostgreSQL Operator](https://github.com/crunchydata/postgres-operator) is an open source project hosted on GitHub.
 
 This guide is intended for those wanting to build the Operator from source or contribute via pull requests.
 
 
 # Prerequisites
+
 The target development host for these instructions is a CentOS 7 or RHEL 7 host. Others operating systems
 are possible, however we do not support building or running the Operator on others at this time.
 
@@ -66,7 +67,6 @@ The setup target ensures the presence of:
 * NSQ messaging binaries
 * `docker` container tool
 * `buildah` OCI image building tool
-* `expenv` config tool
 
 By default, docker is not configured to run its daemon. Refer to the [docker post-installation instructions](https://docs.docker.com/install/linux/linux-postinstall/) to configure it to run once or at system startup. This is not done automatically.
 

docs/content/Upgrade/upgrade4xto42_ansible.md

@@ -0,0 +1,22 @@
+---
+title: "Installation"
+date:
+draft: false
+weight: 40
+---
+
+There are several different ways to install and deploy the [PostgreSQL Operator](https://www.crunchydata.com/developers/download-postgres/containers/postgres-operator)
+based upon your use case.
+
+For the vast majority of use cases, we recommend using the [PostgreSQL Operator Installer]({{< relref "/installation/postgres-operator-installer/_index.md" >}}),
+which uses the `pgo-deployer` container to set up all of the objects required to
+run the PostgreSQL Operator.
+
+For advanced use cases, such as for development, one may want to set up a
+[development environment]({{< relref "/contributing/developer-setup.md" >}})
+that is created using a series of scripts controlled by the Makefile.
+
+Before selecting your installation method, it's important that you first read
+the [prerequisites]({{< relref "/installation/prerequisites.md" >}}) for your
+deployment environment to ensure that your setup meets the needs for installing
+the PostgreSQL Operator.