final doc updates and clean up deprecated directory

Author: Jeff McCormick

README.asciidoc

@@ -25,36 +25,29 @@ The PostgreSQL Operator leverages Kubernetes Custom Resource Definitions to defi
  * *pgbackups*
  * *pgpolicies*
 
-Once those custom objects are defined, Kubernetes provides the ability to create and manage those objects similar to any other native Kubernetes object.
+Kubernetes provides the ability to create and manage Custom Resource Definitions similar to any other native Kubernetes object.
 
-The PostgreSQL Operator runs within Kubernetes detecting these new custom object types being created, updated, or removed.
+The PostgreSQL Operator runs within Kubernetes detecting these custom object types as they are created, updated, or removed.
 
-Once the objects are detected, the PostgreSQL Operator enables users to perform operations across the Kubernetes environment, including:
+The PostgreSQL Operator enables users to perform operations, including:
 
-* Create a PostgreSQL Cluster
-* Destroy a PostgreSQL Cluster
-* Backup a PostgreSQL Cluster
-* Scale a a PostgreSQL Cluster
-* Restore a PostgreSQL Cluster
+* Create, Delete, Scale, Restore, and Backup a PostgreSQL Cluster
 * Upgrade a PostgreSQL Cluster
-* View PVC
+* View PVCs used by PostgreSQL clusters
 * Test Connections to a PostgreSQL Cluster
-* Create a SQL-based Policy
-* Apply a SQL-based Policy to a PostgreSQL Cluster
-* Perform User Management
+* Create and apply a SQL-based Policy to a PostgreSQL Cluster
+* Perform User and Password Management
 * Apply User Defined Labels to PostgreSQL Clusters
-* Perform Password Management
 
 
 [#Requirements]
 == Requirements
 
-CRD (custom resource definitions) are supported starting with Kube 1.7.X.
-NOTE:  Along with this new major version, changes were made to the configuration
-settings from the prior version of the Operator. 
+CRD (custom resource definitions) are supported starting with Kube 1.7.X and
+with the PostgreSQL Operator version 2.0.
 
 If you require an older version of Kube (< 1.7), you can work
-with the operator version 1.5.2 which resides in the github 1.5.X branch.
+with the PostgreSQL Operator version 1.5.2 which resides in the github 1.5.X branch.
 Note however, that the older operator will be deprecated and no longer 
 maintained in the future.
 
@@ -171,11 +164,10 @@ pgo apply policy1 --selector=name=mycluster
 Details on the *pgo* commands and complex examples are found in the
 link:docs/user-guide.asciidoc[User Guide]
 
-#PostgreSQL Operator Container]
 == PostgreSQL Operator Container
 
-The following diagram depicts the components of the PostgreSQL Operator:
-, the PostgreSQL operator client, *pgo*, is
+The following diagram depicts the components of the PostgreSQL Operator,
+here the PostgreSQL operator client, *pgo*, is
 shown interacting with the PostgreSQL operator that runs within
 a Kubernetes cluster.  The operator is responsible for creating
 or modifying PostgreSQL databases deployed within the Kubernetes cluster.

examples/operator/remove-crd.sh deploy/remove-crd.shexamples/operator/remove-crd.sh renamed to deploy/remove-crd.sh

@@ -363,7 +363,7 @@ the following:
  * repeat testing using create storage type
  * repeat testing using existing storage type
  * create a series of clusters  (*pgo create cluster myseries --series=2*)
- * TODO apply policies at cluster creation (*pgo create cluster xraydb --series=2 --labels=project=xray --policies=xrayapp,rlspolicy*)
+ * apply labels at cluster creation (*pgo create cluster xraydb --series=2 --labels=project=xray*)
  * apply a label to an existing set of clusters (*pgo label --label=env=research --selector=project=xray*)
  * create a user for a given cluster (*pgo user --add-user=user0 --valid-days=30 --managed --db=userdb --selector=name=xraydb0*)
  * load a csv file into a cluster (*pgo load --load-config=./sample-load-config.json --selector=project=xray*)

examples/operator/show-crd.sh deploy/show-crd.shexamples/operator/show-crd.sh renamed to deploy/show-crd.sh

@@ -11,10 +11,10 @@ Starting with Operator version 2.1, the *pgo.yaml* configuration
 file is used solely by the *apiserver* and has no effect on the *pgo* client.  With this change, the Operator configuration is centralized to
 the *apiserver* container which is deployed alongside the *postgres-operator* container.
 
-Sample pgo configuration files for various storage configurations are located in the $COROOT/examples directory.
+Sample Operator configuration files for various storage configurations are located in the $COROOT/examples directory.
 
 To configure the Operator, modify the settings found in
-$COROOT/conf/apiserver/pgo.yaml to meet your project needs.  Typically
+*$COROOT/conf/apiserver/pgo.yaml* to meet your project needs.  Typically
 you will modify the storage and namespace settings.
 
 === pgo Configuration Format
@@ -24,10 +24,9 @@ The default pgo configuration file, included in
 
 [source,yaml]
 ....
-Kubeconfig:  /etc/kubernetes/admin.conf
 Namespace:  demo
 Cluster:
-  CCPImageTag:  centos7-10.0-1.6.0
+  CCPImageTag:  centos7-9.6.5-1.6.0
   Port:  5432
   PrimaryPassword:  password
   User:  testuser
@@ -64,7 +63,6 @@ Values in the pgo configuration file have the following meaning:
 [width="90%",cols="m,2",frame="topbot",options="header"]
 |======================
 |Setting | Definition
-|Kubeconfig        | the path to the kubeconfig file
 |Namespace        | the namespace the Operator will run within
 |Cluster.CCPImageTag        |newly created containers will be based on this image version (e.g. centos7-9.6.5-1.6.0), 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)