anchor.diff:  * link:https://hub.docker.com/r/crunchydata/crunchy-backup/[PostgreSQL Backup Container]
   * link:https://hub.docker.com/r/crunchydata/crunchy-upgrade/[PostgreSQL Upgrade Container]
   
  +== Build and Setup Instructions
  +
  +With the operator deployed, the *pgo* command line
  +interface can execute commands that the *postgres-operator* understands
  +and reacts to.
  +
  +You can download a pre-built *pgo* CLI binary from
  +the link:https://github.com/CrunchyData/postgres-operator/releases[Releases] page on the github repository or build
  +it yourself using the build instructions, documented on the link:docs/build.asciidoc[Build and Setup] page.
  +
  +== Configuration
  +
  +You can configure both the client and the operator.  The
  +configuration options are documented on the link:docs/config.asciidoc[Configuration] page.
  +
   == Example Commands Usage
   
  -Some examples of using the command line interface:
  +Some examples of using the *pgo* command line interface are as follows.
   
   .Display Cluster Information
   [source,bash]
  
positive.code: * Test Connections
  * Clone a Cluster
  
  What actually gets created on the Kube cluster for a 
  *pgcluster* resource is defined as a *deployment strategy*.  Strategies
  are documented in detail here link:docs/strategies.asciidoc[Deployment Strategies] 
  
  == Requirements
  
  
negative.code: 
  The PostgreSQL Operator leverages Kubernetes Third Party Resources to define custom resource type *pgcluster*, *pgbackups*, and *pgupgrades*.
  
  Once those custom objects are defined, Kubernetes provides the ability to create and manage those objects similar to any other native Kubernetes object.
  
  The PostgreSQL Operator runs within Kubernetes detecting these new custom object types being created or removed.
  
  Once the objects are detected, the PostgreSQL Operator enables users to perform operations across the Kubernetes environment, including:
  
  