tweak docs and update version to 3.1

Author: Jeff McCormick

hugo/content/installation/configuration.adoc

@@ -6,7 +6,7 @@ weight: 60
 ---
 
 :toc:
-v3.0, {docdate}
+v3.1, {docdate}
 
 == Overview
 
@@ -37,11 +37,11 @@ deployment.
 
 [WARNING]
 ====
-If you are not using the *demo* namespace, it will be required to edit the following and change the namespace where the service account and cluster role bindings will be deployed.
-
-`$COROOT/deploy/service-account.yaml`
-
-`$COROOT/deploy/cluster-role-binding.yaml`
+The CO_NAMESPACE environment variable determines the namespace
+that is used within the deployment of the operator.  If you
+are deploying to the *demo* namespace, the following
+should setting should be defined in your .bashrc:
+`export CO_NAMESPACE=demo`
 ====
 
 {{% notice tip %}}

hugo/content/installation/deployment.adoc

@@ -6,7 +6,7 @@ weight: 50
 ---
 
 :toc:
-v3.0, {docdate}
+v3.1, {docdate}
 
 This document details verifying the installation of the PostgreSQL Operator
 is successful, in addition to detailing some different storage configurations
@@ -53,7 +53,7 @@ The complete set of environment variables used in the installation
 so far are -
 ....
 export CO_IMAGE_PREFIX=crunchydata
-export CO_IMAGE_TAG=centos7-3.0
+export CO_IMAGE_TAG=centos7-3.1
 export GOPATH=$HOME/odev
 export GOBIN=$GOPATH/bin
 export PATH=$PATH:$GOBIN
@@ -130,8 +130,8 @@ pgo version
 At this point you should be able to connect to the operator as follows -
 ....
 pgo version
-pgo client version 3.0
-apiserver version 3.0
+pgo client version 3.1
+apiserver version 3.1
 ....
 
 Operator commands are documented on the link:/getting-started/[Getting Started] page.

hugo/content/installation/helm-chart.adoc

@@ -5,15 +5,15 @@ draft: false
 weight: 30
 ---
 
-v3.0, {docdate}
+v3.1, {docdate}
 
 == Helm Chart
 
 First, pull prebuilt versions from Dockerhub of the *postgres-operator* containers,
 specify the image versions, and execute the following Makefile target -
 ....
 export CO_IMAGE_PREFIX=crunchydata
-export CO_IMAGE_TAG=centos7-3.0
+export CO_IMAGE_TAG=centos7-3.1
 make pull
 ....
 

hugo/content/installation/manual-installation.adoc

@@ -6,7 +6,7 @@ weight: 20
 ---
 
 :toc:
-v3.0, {docdate}
+v3.1, {docdate}
 
 == Project Structure
 
@@ -18,10 +18,16 @@ export CO_NAMESPACE=demo
 export CO_CMD=kubectl
 export COROOT=$GOPATH/src/github.com/crunchydata/postgres-operator
 export CO_IMAGE_PREFIX=crunchydata
-export CO_IMAGE_TAG=centos7-3.0
+export CO_IMAGE_TAG=centos7-3.1
 export CO_BASEOS=centos7
 ....
 
+When deploying on Openshift Container Platform, the CO_CMD environment
+variable should be:
+....
+export CO_CMD=oc
+....
+
 To perform an installation of the operator, first create the project structure as follows on your host, here we assume a local directory called *odev* -
 ....
 mkdir -p $HOME/odev/src $HOME/odev/bin $HOME/odev/pkg
@@ -33,7 +39,7 @@ Next, get a tagged release of the source code -
 cd $GOPATH/src/github.com/crunchydata
 git clone https://github.com/CrunchyData/postgres-operator.git
 cd postgres-operator
-git checkout 3.0
+git checkout 3.1
 ....
 
 == Installation Prerequsites
@@ -51,16 +57,13 @@ kubectl config view | grep namespace
 
 [WARNING]
 ====
-If you are not using the *demo* namespace, it will be required to edit the following and change the namespace where the service account and cluster role bindings will be deployed.
-
-`$COROOT/deploy/service-account.yaml`
-
-`$COROOT/deploy/cluster-role-binding.yaml`
+The namespace used by the operator is determined by the
+CO_NAMESPACE environment variable setting.
 ====
 
 Permissions are granted to the Operator by means of a Service Account called *postgres-operator*.  That service account is added to the Operator deployment.
 
-The postgres-operator service account is granted cluster-admin priviledges using a cluster role binding *postgres-operator-cluster-role-binding*.
+The postgres-operator service account is granted priviledges using a role binding *pgo-role-binding*.
 
 See link:https://kubernetes.io/docs/admin/authorization/rbac/[here] for more details on how to enable RBAC roles and modify the scope of the permissions to suit your needs.
 
@@ -96,10 +99,10 @@ make pull
 To pull down the prebuilt *pgo* binaries, download the *tar.gz* release file from the following link -
 
  * link:https://github.com/CrunchyData/postgres-operator/releases[Github Releases]
- * extract (e.g. tar xvzf postgres-operator.3.0.tar.gz)
+ * extract (e.g. tar xvzf postgres-operator.3.1.tar.gz)
 ....
 cd $HOME
-tar xvzf ./postgres-operator.3.0.tar.gz
+tar xvzf ./postgres-operator.3.1.tar.gz
 ....
  * copy *pgo* client to somewhere in your path (e.g. cp pgo /usr/local/bin)
 

hugo/content/installation/quick-installation.adoc

@@ -6,7 +6,7 @@ weight: 10
 ---
 
 :toc:
-v3.0, {docdate}
+v3.1, {docdate}
 
 == Overview
 

hugo/content/installation/upgrading-the-operator.adoc

@@ -5,7 +5,7 @@ draft: false
 weight: 40
 ---
 
-v3.0, {docdate}
+v3.1, {docdate}
 
 {{%expand "Upgrading from v2.4 to v2.5" %}}
 
@@ -52,7 +52,7 @@ $COROOT/bin/upgrade-secret.sh
 
 For a full list of additions and revisions that occurred in the
 PostgreSQL Operator v2.5 release, please view the related release
-page link:https://github.com/CrunchyData/postgres-operator/releases/tag/3.0[here].
+page link:https://github.com/CrunchyData/postgres-operator/releases/tag/3.1[here].
 
 == Required Updates