Initial attempt at updating references for 2.6 release

Author: crunchyheath

centos7/Dockerfile.pgo-load.centos7

@@ -3,7 +3,7 @@ FROM centos:7
 LABEL name="crunchydata/pgo-load" \
         vendor="crunchy data" \
       	PostgresVersion="9.6" \
-      	PostgresFullVersion="9.6.6" \
+      	PostgresFullVersion="9.6.8" \
         version="7.3" \
         release="2.6" \
         build-date="2018-03-30" \

chart/postgres-operator/files/apiserver/pgo.yaml

@@ -1,6 +1,6 @@
 Cluster:
   CCPImagePrefix:  crunchydata
-  CCPImageTag:  centos7-10.3-1.8.1
+  CCPImageTag:  centos7-10.3-1.8.2
   Port:  5432
   User:  testuser
   Database:  userdb

docs/design.asciidoc

@@ -1,6 +1,6 @@
 = postgres Operator Design
 :toc:
-v2.5, {docdate}
+v2.6, {docdate}
 
 
 image::crunchy_logo.png?raw=true[]

docs/gke-notes.asciidoc

@@ -1,6 +1,6 @@
 = GKE Notes
 :toc:
-v2.5, {docdate}
+v2.6, {docdate}
 
 == Overview
 

docs/operator-docs.asciidoc

@@ -131,16 +131,16 @@ containers, you can pre-pull them as follows:
 
 For PostgreSQL version 10:
 ....
-docker pull crunchydata/crunchy-postgres:centos7-10.3-1.8.1
-docker pull crunchydata/crunchy-backup:centos7-10.3-1.8.1
-docker pull crunchydata/crunchy-upgrade:centos7-10.3-1.8.1
+docker pull crunchydata/crunchy-postgres:centos7-10.3-1.8.2
+docker pull crunchydata/crunchy-backup:centos7-10.3-1.8.2
+docker pull crunchydata/crunchy-upgrade:centos7-10.3-1.8.2
 ....
 
 For PostgreSQL version 9.6:
 ....
-docker pull crunchydata/crunchy-postgres:centos7-9.6.8-1.8.1
-docker pull crunchydata/crunchy-backup:centos7-9.6.8-1.8.1
-docker pull crunchydata/crunchy-upgrade:centos7-9.6.8-1.8.1
+docker pull crunchydata/crunchy-postgres:centos7-9.6.8-1.8.2
+docker pull crunchydata/crunchy-backup:centos7-9.6.8-1.8.2
+docker pull crunchydata/crunchy-upgrade:centos7-9.6.8-1.8.2
 ....
 
 === Get Prebuilt Images
@@ -543,7 +543,7 @@ The default pgo configuration file, included in
 ....
 BasicAuth:  true
 Cluster:
-  CCPImageTag:  centos7-10.3-1.8.1
+  CCPImageTag:  centos7-10.3-1.8.2
   Port:  5432
   User:  testuser
   Database:  userdb
@@ -595,7 +595,7 @@ Values in the pgo configuration file have the following meaning:
 |======================
 |Setting | Definition
 |BasicAuth        | if set to *true* will enable Basic Authentication
-|Cluster.CCPImageTag        |newly created containers will be based on this image version (e.g. centos7-10.3-1.8.1), unless you override it using the --ccp-image-tag command line flag
+|Cluster.CCPImageTag        |newly created containers will be based on this image version (e.g. centos7-10.3-1.8.2), unless you override it using the --ccp-image-tag command line flag
 |Cluster.Port        | the PostgreSQL port to use for new containers (e.g. 5432)
 |Cluster.User        | the PostgreSQL normal user name
 |Cluster.Strategy        | sets the deployment strategy to be used for deploying a cluster, currently there is only strategy *1*
@@ -858,7 +858,7 @@ pgo show cluster all
 
 You can filter the results based on the Postgres Version:
 ....
-pgo show cluster all --version=9.6.2
+pgo show cluster all --version=9.6.8
 ....
 
 You can also add metrics collection to a cluster by using the *--metrics*
@@ -877,7 +877,7 @@ based on the *pgo* configuration file's CCP_IMAGE_TAG setting.  You
 can override this value using the *--ccp-image-tag* command line
 flag:
 ....
-pgo create cluster mycluster --ccp-image-tag=centos7-9.6.5-1.6.0
+pgo create cluster mycluster --ccp-image-tag=centos7-9.6.8-1.8.2
 ....
 
 You can also add a pgpool deployment into a cluster by using the *--pgpool*
@@ -1019,7 +1019,7 @@ pgo show cluster all
 
 You can filter the results by Postgres version:
 ....
-pgo show cluster all --version=9.6.2
+pgo show cluster all --version=9.6.8
 ....
 
 The scale command will let you specify a *--node-label* flag which
@@ -1089,8 +1089,8 @@ job to know when and how to proceed.
 
 Likewise, you can upgrade the cluster using a command line flag:
 ....
-pgo upgrade mycluster --ccp-image-tag=centos7-9.6.8-1.8.1
-pgo upgrade mycluster --upgrade-type=major --ccp-image-tag=centos7-9.6.8-1.8.1
+pgo upgrade mycluster --ccp-image-tag=centos7-9.6.8-1.8.2
+pgo upgrade mycluster --upgrade-type=major --ccp-image-tag=centos7-9.6.8-1.8.2
 ....
 
 

docs/operator-testing.asciidoc

@@ -17,7 +17,7 @@ the following:
  * show backup of cluster (*pgo show backup testcluster*)
  * show backup pvc of cluster (*pgo show pvc testcluster-backup-pvc*)
  * restore a cluster (*pgo create cluster restoredcluster --backup-pvc=testcluster-backup-pvc --backup-path=testcluster-backups/2017-01-01-01-01-01 --secret-from=testcluster*)
- * create cluster using image tag (*pgo create minor --ccp-image-tag=cenots7-10.3-1.8.1*)
+ * create cluster using image tag (*pgo create minor --ccp-image-tag=cenots7-10.3-1.8.2*)
  * minor upgrade a cluster (*pgo upgrade minor*)
  * delete a cluster (*pgo delete cluster restored --delete-data --delete-backups*)
  * create a policy from local file (*pgo create policy xrayapp --in-file=./examples/policy/xrayapp.sql*)

examples/pgo.yaml.emptydir

@@ -1,7 +1,7 @@
 Namespace:  demo
 Cluster:
   CCPImagePrefix:  crunchydata
-  CCPImageTag:  centos7-10.3-1.8.1
+  CCPImageTag:  centos7-10.3-1.8.2
   Port:  5432
   User:  testuser
   Database:  userdb

examples/pgo.yaml.hostpath

@@ -1,5 +1,5 @@
 Cluster:
-  CCPImageTag:  centos7-10.3-1.8.1
+  CCPImageTag:  centos7-10.3-1.8.2
   Port:  5432
   User:  testuser
   Database:  userdb

examples/pgo.yaml.nfs

@@ -1,6 +1,6 @@
 Cluster:
   CCPImagePrefix:  crunchydata
-  CCPImageTag:  centos7-10.3-1.8.1
+  CCPImageTag:  centos7-10.3-1.8.2
   Port:  5432
   User:  testuser
   Database:  userdb

examples/pgo.yaml.storageclass

@@ -1,6 +1,6 @@
 Cluster:
   CCPImagePrefix:  crunchydata
-  CCPImageTag:  centos7-10.3-1.8.1
+  CCPImageTag:  centos7-10.3-1.8.2
   Port:  5432
   User:  testuser
   Database:  userdb