Create "pgo-config" ConfigMap if not provided

The Operator (and associated containers) will create the pgo-config
ConfigMap from the stored default configuration if the pgo-config
ConfigMap is not present.

This allows for the editing of "default configuration" after
the Operator is deployed, and allows for the removal of the
pgo-config creation step from several of the installation
methods.

Issue: [ch9451]

Author: Jonathan S. Katz

docs/content/Configuration/configuration.md

@@ -16,9 +16,9 @@ The configuration files used by the Operator are found in 2 places:
  * the pgo-config ConfigMap in the namespace the Operator is running in
  * or, a copy of the configuration files are also included by default into the Operator container images themselves to support a very simplistic deployment of the Operator
 
-If the pgo-config ConfigMap is not found by the Operator, it will use
-the configuration files that are included in the Operator container
-images.
+If the `pgo-config` ConfigMap is not found by the Operator, it will create a
+`pgo-config` ConfigMap using the configuration files that are included in the
+Operator container.
 
 ## conf/postgres-operator/pgo.yaml
 The *pgo.yaml* file sets many different Operator configuration settings and is described in the [pgo.yaml configuration]({{< ref "pgo-yaml-configuration.md" >}}) documentation section.

docs/content/installation/other/operator-hub.md

@@ -43,19 +43,6 @@ git clone -b v{{< param operatorVersion >}} https://github.com/CrunchyData/postg
 cd postgres-operator
 ```
 
-### PostgreSQL Operator Configuration
-
-Edit `conf/postgres-operator/pgo.yaml` to configure the deployment. Look over all of the options and make any
-changes necessary for your environment. A full description of each option is available in the
-[`pgo.yaml` configuration guide]({{< relref "configuration/pgo-yaml-configuration.md" >}}).
-
-When the file is ready, upload the entire directory to the `pgo-config` ConfigMap.
-
-```
-kubectl -n "$PGO_OPERATOR_NAMESPACE" create configmap pgo-config \
-  --from-file=./conf/postgres-operator
-```
-
 ### Secrets
 
 Configure pgBackRest for your environment. If you do not plan to use AWS S3 to store backups, you can omit
@@ -152,4 +139,3 @@ pgo version
 # pgo client version {{< param operatorVersion >}}
 # pgo-apiserver version {{< param operatorVersion >}}
 ```
-

installers/olm/description.openshift.md

@@ -63,20 +63,6 @@ edit `conf/postgres-operator/pgo.yaml` and set `DisableFSGroup` to `true`.
 
 [Security Context Constraint]: https://docs.openshift.com/container-platform/latest/authentication/managing-security-context-constraints.html
 
-### PostgreSQL Operator Configuration
-
-Edit `conf/postgres-operator/pgo.yaml` to configure the deployment. Look over all of the options and make any
-changes necessary for your environment. A [full description of each option][pgo-yaml-reference] is available in the documentation.
-
-[pgo-yaml-reference]: https://access.crunchydata.com/documentation/postgres-operator/${PGO_VERSION}/configuration/pgo-yaml-configuration/
-
-When the file is ready, upload the entire directory to the `pgo-config` ConfigMap.
-
-```
-oc -n "$PGO_OPERATOR_NAMESPACE" create configmap pgo-config \
-  --from-file=./conf/postgres-operator
-```
-
 ### Secrets
 
 Configure pgBackRest for your environment. If you do not plan to use AWS S3 to store backups, you can omit

installers/olm/description.upstream.md

@@ -56,20 +56,6 @@ git clone -b v${PGO_VERSION} https://github.com/CrunchyData/postgres-operator.gi
 cd postgres-operator
 ```
 
-### PostgreSQL Operator Configuration
-
-Edit `conf/postgres-operator/pgo.yaml` to configure the deployment. Look over all of the options and make any
-changes necessary for your environment. A [full description of each option][pgo-yaml-reference] is available in the documentation.
-
-[pgo-yaml-reference]: https://access.crunchydata.com/documentation/postgres-operator/${PGO_VERSION}/configuration/pgo-yaml-configuration/
-
-When the file is ready, upload the entire directory to the `pgo-config` ConfigMap.
-
-```
-kubectl -n "$PGO_OPERATOR_NAMESPACE" create configmap pgo-config \
-  --from-file=./conf/postgres-operator
-```
-
 ### Secrets
 
 Configure pgBackRest for your environment. If you do not plan to use AWS S3 to store backups, you can omit