anchor.diff:  
   The operator funtionality runs in a Pod deployed to your
   Kubernetes cluster.  The *postgres-operator* Docker container
  -is available on link:https://hub.docker.com/r/crunchydata/postgres-operator/[Dockerhub].  
  +is available on link:https://hub.docker.com/r/crunchydata/postgres-operator/[Dockerhub].
   
   You can also build the Docker image for *postgres-operator* using
  -the build instructions link:docs/build.asciidoc[Build and Setup].
  -
  -== Command Line Interface
  -
  -With the operator deployed, you can then use the *pgo* command line 
  -interface to execute commands that the *postgres-operator* understands 
  -and reacts to.
  -
  -You can download a pre-built *pgo* CLI binary from 
  -the Releases page on the github repository or build
  -it yourself using the build instructions.
  -
  -
  -== Build and Setup Instructions
  -
  -Build instructions are documented here.
  -link:docs/build.asciidoc[Build and Setup] 
  -
  -== Configuration
  -
  -You can configure both the client and the operator.  The
  -configuration options are documented here.
  -link:docs/config.asciidoc[Configuration]
  -
  -
  +the build instructions located on the link:docs/build.asciidoc[Build and Setup] page.
  
positive.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:
  
  
negative.code: .Upgrade Cluster (minor Postgres version upgrade)
  [source,bash]
  ----
  pgo create upgrade mycluster
  ----
  
  .Upgrade Cluster (major Postgres version upgrade from 9.5 to 9.6)
  