Update general descriptions

This provides some updates around the geneal description for
PGO.

Author: Jonathan S. Katz

README.md

@@ -1,17 +1,22 @@
-<h1 align="center">Crunchy Data PostgreSQL Operator</h1>
+<h1 align="center">PGO: The Postgres Operator from Crunchy Data</h1>
 <p align="center">
   <img width="150" src="crunchy_logo.png" alt="Crunchy Data"/>
 </p>
 
 [![Go Report Card](https://goreportcard.com/badge/github.com/CrunchyData/postgres-operator)](https://goreportcard.com/report/github.com/CrunchyData/postgres-operator)
 
-# Run your own production-grade PostgreSQL-as-a-Service on Kubernetes!
+# Run Cloud Native PostgreSQL on Kubernetes with PGO: The Postgres Operator from Crunchy Data!
 
-The [Crunchy PostgreSQL Operator][documentation] automates and simplifies deploying and managing
-open source PostgreSQL clusters on Kubernetes and other Kubernetes-enabled Platforms by providing
-the essential features you need to keep your PostgreSQL clusters up and running, including:
+[PGO][documentation], the [Postgres Operator][documentation] developed by
+[Crunchy Data](https://crunchydata.com/) and included in [Crunchy PostgreSQL for Kubernetes](https://www.crunchydata.com/products/crunchy-postgresql-for-kubernetes/), automates and simplifies deploying and managing open source
+PostgreSQL clusters on Kubernetes.
 
-#### PostgreSQL Cluster [Provisioning][provisioning]
+Whether you need to get a simple Postgres cluster up and running, need to deploy
+a high availability, fault tolerant cluster in production, or are running your
+own database-as-a-service, the PostgreSQL Operator provides the essential
+features you need to keep your cloud native Postgres clusters healthy, including:
+
+#### Postgres Cluster [Provisioning][provisioning]
 
 [Create, Scale, & Delete PostgreSQL clusters with ease][provisioning], while fully customizing your
 Pods and PostgreSQL configuration!
@@ -33,7 +38,7 @@ Set how long you want your backups retained for. Works great with very large dat
 #### TLS
 
 Secure communication between your applications and data servers by [enabling TLS for your PostgreSQL servers][pgo-task-tls],
-including the ability to enforce that all of your connections to use TLS.
+including the ability to enforce all of your connections to use TLS.
 
 #### [Monitoring][monitoring]
 
@@ -76,16 +81,22 @@ the S3 protocol. The PostgreSQL Operator can backup, restore, and create new clu
 
 #### Multi-Namespace Support
 
-You can control how the PostgreSQL Operator leverages [Kubernetes Namespaces][k8s-namespaces] with several different deployment models:
+You can control how PGO, the Postgres Operator, leverages [Kubernetes Namespaces][k8s-namespaces] with several different deployment models:
 
-- Deploy the PostgreSQL Operator and all PostgreSQL clusters to the same namespace
-- Deploy the PostgreSQL Operator to one namespaces, and all PostgreSQL clusters to a different namespace
-- Deploy the PostgreSQL Operator to one namespace, and have your PostgreSQL clusters managed across multiple namespaces
-- Dynamically add and remove namespaces managed by the PostgreSQL Operator using the `pgo create namespace` and `pgo delete namespace` commands
+- Deploy PGO and all PostgreSQL clusters to the same namespace
+- Deploy PGO to one namespaces, and all PostgreSQL clusters to a different
+namespace
+- Deploy PGO to one namespace, and have your PostgreSQL clusters managed across
+multiple namespaces
+- Dynamically add and remove namespaces managed by the PostgreSQL Operator using
+the `pgo` client to run `pgo create namespace` and `pgo delete namespace`
 
 #### Full Customizability
 
-The Crunchy PostgreSQL Operator makes it easy to get your own PostgreSQL-as-a-Service up and running on Kubernetes-enabled platforms, but we know that there are further customizations that you can make. As such, the Crunchy PostgreSQL Operator allows you to further customize your deployments, including:
+The Postgres Operator (PGO) makes it easy to get Postgres up and running on
+Kubernetes-enabled platforms, but we know that there are further customizations
+that you can make. As such, PGO allows you to further customize your
+deployments, including:
 
 - Selecting different storage classes for your primary, replica, and backup storage
 - Select your own container resources class for each PostgreSQL cluster deployment; differentiate between resources applied for primary and replica clusters!
@@ -94,7 +105,6 @@ The Crunchy PostgreSQL Operator makes it easy to get your own PostgreSQL-as-a-Se
 - Bring your own trusted certificate authority (CA) for use with the Operator API server
 - Override your PostgreSQL configuration for each cluster
 
-
 [disaster-recovery]: https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/disaster-recovery/
 [disaster-recovery-s3]: https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/disaster-recovery/#using-s3
 [disaster-recovery-scheduling]: https://access.crunchydata.com/documentation/postgres-operator/latest/architecture/disaster-recovery/#scheduling-backups
@@ -117,47 +127,58 @@ The Crunchy PostgreSQL Operator makes it easy to get your own PostgreSQL-as-a-Se
 
 ## Deployment Requirements
 
-The PostgreSQL Operator is validated for deployment on Kubernetes, OpenShift, and VMware Enterprise PKS clusters.  Some form of storage is required, NFS, hostPath, and Storage Classes are currently supported.
+PGO, the Postgres Operator, is validated for deployment on Kubernetes,
+OpenShift, GKE, Anthos, AKS, EKS, and VMware Tanzu clusters. PGO is cloud native
+and storage agnostic, working with a wide variety of storage classes, hostPath,
+and NFS.
 
-The PostgreSQL Operator includes various components that get deployed to your
-Kubernetes cluster as shown in the following diagram and detailed
-in the Design section of the documentation for the version you are running.
+PGO includes various components that get deployed to your Kubernetes cluster as
+shown in the following diagram and detailed in the Design section of the
+documentation for the version you are running.
 
 ![Reference](https://access.crunchydata.com/documentation/postgres-operator/latest/Operator-Architecture.png)
 
-The PostgreSQL Operator is developed and tested on CentOS and RHEL linux platforms but is known to run on other Linux variants.
+PGO is developed and tested on CentOS and RHEL linux platforms but is known to
+run on other Linux variants.
 
 ### Supported Platforms
 
-The Crunchy PostgreSQL Operator is tested on the following Platforms:
+PGO, the Postgres Operator, is Kubernetes-native and maintains backwards
+compatibility to Kubernetes 1.11 and is tested is tested against the following
+platforms:
 
 - Kubernetes 1.13+
 - OpenShift 3.11+
 - Google Kubernetes Engine (GKE), including Anthos
 - Amazon EKS
-- VMware Enterprise PKS 1.3+
-
-### Storage
+- Microsoft AKS
+- VMware Tanzu
 
-The Crunchy PostgreSQL Operator is tested with a variety of different types of Kubernetes storage and Storage Classes, including:
+This list only includes the platforms that the Postgres Operator is specifically
+tested on as part of the release process: PGO works on other Kubernetes
+distributions as well.
 
-- Google Compute Engine persistent volumes
-- HostPath
-- NFS
-- Rook
-- StorageOS
+### Storage
 
-and more.
+PGO, the Postgres Operator, is tested with a variety of different types of
+Kubernetes storage and Storage Classes, as well as hostPath and NFS.
 
-We know there are a variety of different types of [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) available for Kubernetes and we do our best to test each one, but due to the breadth of this area we are unable to verify PostgreSQL Operator functionality in each one. With that said, the PostgreSQL Operator is designed to be storage class agnostic and has been demonstrated to work with additional Storage Classes.
+We know there are a variety of different types of [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/)
+available for Kubernetes and we do our best to test each one, but due to the
+breadth of this area we are unable to verify Postgres Operator functionality in
+each one. With that said, the PostgreSQL Operator is designed to be storage
+class agnostic and has been demonstrated to work with additional Storage
+Classes.
 
 ## Installation
 
-### PostgreSQL Operator Installation
+### Postgres Operator (PGO) Installation
 
-The PostgreSQL Operator provides a few different methods for installation based on your use case.
+PGO provides a few different methods for installation methods to get up and
+running with cloud native Postgres.
 
-Based on your storage settings in your Kubernetes environment, you may be able to start as quickly as:
+Based on your storage settings in your Kubernetes environment, you may be able
+to start as quickly as:
 
 ```shell
 kubectl create namespace pgo
@@ -176,7 +197,7 @@ Installations methods include:
 
 ### `pgo` Client Installation
 
-If you have the PostgreSQL Operator installed in your environment, and are interested in installation of the client interface, please start here:
+If you have the Postgres Operator installed in your environment, and are interested in installation of the client interface, please start here:
 
 - [pgo Client Install](https://access.crunchydata.com/documentation/postgres-operator/latest/installation/pgo-client/)
 
@@ -223,16 +244,24 @@ Additional containers that are not directly integrated with the PostgreSQL Opera
 
 For more information about which versions of the PostgreSQL Operator include which components, please visit the [compatibility](https://access.crunchydata.com/documentation/postgres-operator/latest/configuration/compatibility/) section of the documentation.
 
-## Using the PostgreSQL Operator
+## Using the PostgreSQL Operator (PGO)
+
+If you are new to PGO, you can follow along the [tutorial](https://access.crunchydata.com/documentation/postgres-operator/latest/tutorial/)
+to learn how to install the PostgreSQL Operator and how to use many of its
+features!
 
-If you have the PostgreSQL and Client Interface installed in your environment and are interested in guidance on the use of the Crunchy PostgreSQL Operator, please start here:
+- [PostgreSQL Operator Tutorial](https://access.crunchydata.com/documentation/postgres-operator/latest/tutorial/)
 
-- [PostgreSQL Operator Documentation](https://access.crunchydata.com/documentation/postgres-operator/)
+If you have the PostgreSQL and client interface installed in your environment
+and are interested in guidance on the use of the Crunchy PostgreSQL Operator,
+please start here:
+
+- [PostgreSQL Operator (PGO) Documentation](https://access.crunchydata.com/documentation/postgres-operator/)
 - [`pgo` Client User Guide](https://access.crunchydata.com/documentation/postgres-operator/latest/pgo-client/)
 
 ## Contributing to the Project
 
-Want to contribute to the PostgreSQL Operator project? Great! We've put together
+Want to contribute to the PGO Project? Great! We've put together
 as set of contributing guidelines that you can review here:
 
 - [Contributing Guidelines](CONTRIBUTING.md)
@@ -265,7 +294,7 @@ For other information, please visit the [Support](https://access.crunchydata.com
 ## Documentation
 
 For additional information regarding design, configuration and operation of the
-PostgreSQL Operator, pleases see the [Official Project Documentation][documentation].
+PostgreSQL Operator (PGO), please see the [Official Project Documentation][documentation].
 
 If you are looking for the [nightly builds of the documentation](https://crunchydata.github.io/postgres-operator/latest/), you can view them at:
 
@@ -276,3 +305,16 @@ https://crunchydata.github.io/postgres-operator/latest/
 ## Past Versions
 
 Documentation for previous releases can be found at the [Crunchy Data Access Portal](https://access.crunchydata.com/documentation/)
+
+## Releases
+
+When a PGO general availability (GA) release occurs, the container images are
+distributed on the following platforms in order:
+
+- [Crunchy Data Customer Portal](https://access.crunchydata.com/)
+- [Crunchy Data Developer Portal](https://www.crunchydata.com/developers)
+- [DockerHub](https://hub.docker.com/u/crunchydata)
+
+The image rollout can occur over the course of several days.
+
+To stay up-to-date on when releases are made available in the [Crunchy Data Developer Portal](https://www.crunchydata.com/developers), please sign up for the [Crunchy Data Developer Program Newsletter](https://www.crunchydata.com/developers/newsletter)

docs/config.toml

@@ -2,7 +2,7 @@ baseURL= ""
 
 languageCode = "en-us"
 DefaultContentLanguage = "en"
-title = "Crunchy PostgreSQL Operator Documentation"
+title = "PGO: PostgreSQL Operator from Crunchy Data Documentation"
 theme = "crunchy-hugo-theme"
 pygmentsCodeFences = true
 pygmentsStyle = "monokailight"

docs/content/_index.md

@@ -1,20 +1,30 @@
 ---
-title: "Crunchy PostgreSQL Operator"
+title: "PGO: The Postgres Operator from Crunchy Data"
 date:
 draft: false
 ---
 
-# Crunchy PostgreSQL Operator
+# PGO: The Postgres Operator from Crunchy Data
 
  <img width="25%" src="crunchy_logo.png"/>
 
-## Run your own production-grade PostgreSQL-as-a-Service on Kubernetes!
+## Run [Cloud Native PostgreSQL on Kubernetes](https://www.crunchydata.com/products/crunchy-postgresql-for-kubernetes/) with PGO: The [Postgres Operator](https://github.com/CrunchyData/postgres-operator) from [Crunchy Data](https://www.crunchydata.com/)!
 
 Latest Release: {{< param operatorVersion >}}
 
-The [Crunchy PostgreSQL Operator](https://www.crunchydata.com/developers/download-postgres/containers/postgres-operator) automates and simplifies deploying and managing open source PostgreSQL clusters on Kubernetes and other Kubernetes-enabled Platforms by providing the essential features you need to keep your PostgreSQL clusters up and running, including:
+[PGO](https://www.crunchydata.com/developers/download-postgres/containers/postgres-operator),
+the [Postgres Operator](https://github.com/CrunchyData/postgres-operator)
+developed by [Crunchy Data](https://crunchydata.com/) and included in
+[Crunchy PostgreSQL for Kubernetes](https://www.crunchydata.com/products/crunchy-postgresql-for-kubernetes/),
+automates and simplifies deploying and managing open source PostgreSQL clusters
+on Kubernetes.
 
-#### PostgreSQL Cluster [Provisioning]({{< relref "/architecture/provisioning.md" >}})
+Whether you need to get a simple Postgres cluster up and running, need to deploy
+a high availability, fault tolerant cluster in production, or are running your
+own database-as-a-service, the PostgreSQL Operator provides the essential
+features you need to keep your cloud native Postgres clusters healthy, including:
+
+#### Postgres Cluster [Provisioning]({{< relref "/architecture/provisioning.md" >}})
 
 [Create, Scale, & Delete PostgreSQL clusters with ease](/architecture/provisioning/), while fully customizing your Pods and PostgreSQL configuration!
 
@@ -30,7 +40,7 @@ Backups and restores leverage the open source [pgBackRest](https://www.pgbackres
 
 #### TLS
 
-Secure communication between your applications and data servers by [enabling TLS for your PostgreSQL servers](/pgo-client/common-tasks/#enable-tls), including the ability to enforce that all of your connections to use TLS.
+Secure communication between your applications and data servers by [enabling TLS for your PostgreSQL servers](/pgo-client/common-tasks/#enable-tls), including the ability to enforce all of your connections to use TLS.
 
 #### [Monitoring]({{< relref "/architecture/monitoring.md" >}})
 
@@ -72,16 +82,22 @@ Choose the type of backup (full, incremental, differential) and [how frequently
 
 #### Multi-Namespace Support
 
-You can control how the PostgreSQL Operator leverages [Kubernetes Namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) with several different deployment models:
+You can control how PGO, the Postgres Operator, leverages [Kubernetes Namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) with several different deployment models:
 
-- Deploy the PostgreSQL Operator and all PostgreSQL clusters to the same namespace
-- Deploy the PostgreSQL Operator to one namespaces, and all PostgreSQL clusters to a different namespace
-- Deploy the PostgreSQL Operator to one namespace, and have your PostgreSQL clusters managed acrossed multiple namespaces
-- Dynamically add and remove namespaces managed by the PostgreSQL Operator using the `pgo create namespace` and `pgo delete namespace` commands
+- Deploy PGO and all PostgreSQL clusters to the same namespace
+- Deploy PGO to one namespaces, and all PostgreSQL clusters to a different
+namespace
+- Deploy PGO to one namespace, and have your PostgreSQL clusters managed across
+multiple namespaces
+- Dynamically add and remove namespaces managed by the PostgreSQL Operator using
+the `pgo` client to run `pgo create namespace` and `pgo delete namespace`
 
 #### Full Customizability
 
-The Crunchy PostgreSQL Operator makes it easy to get your own PostgreSQL-as-a-Service up and running on Kubernetes-enabled platforms, but we know that there are further customizations that you can make. As such, the Crunchy PostgreSQL Operator allows you to further customize your deployments, including:
+The Postgres Operator (PGO) makes it easy to get Postgres up and running on
+Kubernetes-enabled platforms, but we know that there are further customizations
+that you can make. As such, PGO allows you to further customize your
+deployments, including:
 
 - Selecting different storage classes for your primary, replica, and backup storage
 - Select your own container resources class for each PostgreSQL cluster deployment; differentiate between resources applied for primary and replica clusters!
@@ -140,24 +156,29 @@ For more information about which versions of the PostgreSQL Operator include whi
 
 # Supported Platforms
 
-The Crunchy PostgreSQL Operator is tested on the following Platforms:
+PGO, the Postgres Operator, is Kubernetes-native and maintains backwards
+compatibility to Kubernetes 1.11 and is tested is tested against the following
+platforms:
 
 - Kubernetes 1.13+
 - OpenShift 3.11+
 - Google Kubernetes Engine (GKE), including Anthos
 - Amazon EKS
-- VMware Enterprise PKS 1.3+
-
-## Storage
+- Microsoft AKS
+- VMware Tanzu
 
-The Crunchy PostgreSQL Operator is tested with a variety of different types of Kubernetes storage and Storage Classes, including:
+This list only includes the platforms that the Postgres Operator is specifically
+tested on as part of the release process: PGO works on other Kubernetes
+distributions as well.
 
-- Rook
-- StorageOS
-- Google Compute Engine persistent volumes
-- NFS
-- HostPath
+## Storage
 
-and more. We have had reports of people using the PostgreSQL Operator with other [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) as well.
+PGO, the Postgres Operator, is tested with a variety of different types of
+Kubernetes storage and Storage Classes, as well as hostPath and NFS.
 
-We know there are a variety of different types of [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) available for Kubernetes and we do our best to test each one, but due to the breadth of this area we are unable to verify PostgreSQL Operator functionality in each one. With that said, the PostgreSQL Operator is designed to be storage class agnostic and has been demonstrated to work with additional Storage Classes. Storage is a rapidly evolving field in Kubernetes and we will continue to adapt the PostgreSQL Operator to modern Kubernetes storage standards.
+We know there are a variety of different types of [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/)
+available for Kubernetes and we do our best to test each one, but due to the
+breadth of this area we are unable to verify Postgres Operator functionality in
+each one. With that said, the PostgreSQL Operator is designed to be storage
+class agnostic and has been demonstrated to work with additional Storage
+Classes.