Remove CentOS from component documentation

cbandy · cbandy · commit 3e3fd024eadd · 2022-03-28T17:11:13.000-05:00
Issue: [sc-13732]
diff --git a/docs/config.toml b/docs/config.toml
@@ -28,25 +28,20 @@ menushortcutsnewtab = true # set true to open shortcuts links to a new tab/windo
 enableGitInfo = true
 operatorVersion = "5.1.0"
 operatorVersionLatestRel5_0 = "5.0.5"
-centosBase = "centos8"
 imageCrunchyPostgres = "registry.developers.crunchydata.com/crunchydata/crunchy-postgres:centos8-14.1-1"
 imageCrunchyPostgresPrivate = "registry.crunchydata.com/crunchydata/crunchy-postgres:ubi8-14.1-1"
 imageCrunchyPGBackrest = "registry.developers.crunchydata.com/crunchydata/crunchy-pgbackrest:centos8-2.36-1"
 imageCrunchyPGBackrestPrivate = "registry.crunchydata.com/crunchydata/crunchy-pgbackrest:ubi8-2.36-1"
 imageCrunchyPGBouncer = "registry.developers.crunchydata.com/crunchydata/crunchy-pgbouncer:centos8-1.16-1"
 imageCrunchyExporter = "registry.developers.crunchydata.com/crunchydata/crunchy-postgres-exporter:ubi8-5.1.0-0"
 imageCrunchyPGAdmin = "registry.developers.crunchydata.com/crunchydata/crunchy-pgadmin4:centos8-4.20-0"
-repository = "registry.developers.crunchydata.com/crunchydata"
-repositoryPrivate = "registry.com/crunchydata"
+operatorRepository     = "registry.developers.crunchydata.com/crunchydata/postgres-operator"
+operatorRepositoryPrivate         = "registry.crunchydata.com/crunchydata/postgres-operator"
 postgresOperatorTag = "ubi8-5.1.0-0"
 PGBouncerComponentTagUbi8 = "ubi8-1.16-1"
-PGBouncerComponentTagCentos8 = "centos8-1.16-1"
 PGBouncerTagUbi8 = "ubi8-5.1.0-0"
-PGBouncerTagCentos8 = "centos8-5.1.0-0"
 postgres14GIS31ComponentTagUbi8 = "ubi8-14.1-3.1-1"
-postgres14GIS31ComponentTagCentos8 = "centos8-14.1-3.1-1"
 postgres14GIS31TagUbi8 = "ubi8-14.1-3.1-5.1.0-0"
-postgres14GIS31TagCentos8 = "centos8-14.1-3.1-5.1.0-0"
 fromPostgresVersion = "13"
 postgresVersion = "14"
 postgresVersion14 = "14.1"
diff --git a/docs/content/guides/private-registries.md b/docs/content/guides/private-registries.md
@@ -36,7 +36,7 @@ For example, to set up an image pull secret using the [Kustomize install method]
 ```yaml
 images:
 - name: postgres-operator
-  newName: {{< param repositoryPrivate >}}/postgres-operator
+  newName: {{< param operatorRepositoryPrivate >}}
   newTag: {{< param postgresOperatorTag >}}
 
 patchesJson6902:
@@ -74,7 +74,7 @@ and modify the manifest to be the following:
 ```yaml
 images:
 - name: postgres-operator
-  newName: {{< param repositoryPrivate >}}/postgres-operator
+  newName: {{< param operatorRepositoryPrivate >}}
   newTag: {{< param postgresOperatorTag >}}
 
 patchesJson6902:
diff --git a/docs/content/guides/v4tov5.md b/docs/content/guides/v4tov5.md
@@ -389,10 +389,10 @@ For more information on how to use PGO v5, we recommend reading through the [PGO
 ## Additional Considerations
 
 Upgrading to PGO v5 may result in a base image upgrade from EL-7 (UBI / CentOS) to EL-8
-(UBI / CentOS). Based on the contents of your Postgres database, you may need to perform
+(UBI). Based on the contents of your Postgres database, you may need to perform
 additional steps.
 
-Due to changes in the GNU C library (`glibc`) in EL-8, you may need to reindex certain indexes in
+Due to changes in the GNU C library `glibc` in EL-8, you may need to reindex certain indexes in
 your Postgres cluster. For more information, please read the
 [PostgreSQL Wiki on Locale Data Changes](https://wiki.postgresql.org/wiki/Locale_data_changes), how
 you can determine if your indexes are affected, and how to fix them.
diff --git a/docs/content/installation/helm.md b/docs/content/installation/helm.md
@@ -38,7 +38,7 @@ For instance, it might be necessary to customize the image tags that are utilize
 
 ```yaml
 image:
-  image: {{< param repository >}}/postgres-operartor:{{< param postgresOperatorTag >}}
+  image: {{< param operatorRepository >}}:{{< param postgresOperatorTag >}}
 ```
 
 Please note that the `values.yaml` file is located in `helm/install`.
diff --git a/docs/content/installation/kustomize.md b/docs/content/installation/kustomize.md
@@ -38,7 +38,7 @@ in the `kustomize/install/bases/kustomization.yaml` file can be modified:
 ```yaml
 images:
 - name: postgres-operator
-  newName: {{< param repository >}}
+  newName: {{< param operatorRepository >}}
   newTag: {{< param postgresOperatorTag >}}
 ```
 
diff --git a/docs/content/references/components.md b/docs/content/references/components.md
@@ -75,23 +75,19 @@ The container tags follow one of two patterns:
 - `<baseImage>-<softwareVersion>-<buildVersion>`
 - `<baseImage>-<softwareVersion>-<pgoVersion>-<buildVersion>` (Customer Portal only)
 
-For example, if pulling from the [customer portal](https://access.crunchydata.com/), the following would all be valid tags to reference the PgBouncer container:
+For example, when pulling from the [customer portal](https://access.crunchydata.com/), the following would both be valid tags to reference the PgBouncer container:
 
 - `{{< param PGBouncerComponentTagUbi8 >}}`
 - `{{< param PGBouncerTagUbi8 >}}`
-- `{{< param PGBouncerComponentTagCentos8 >}}`
-- `{{< param PGBouncerTagCentos8 >}}`
 
-The [developer portal](https://www.crunchydata.com/developers/download-postgres/containers) provides CentOS based images. For example, PgBouncer would use this tag:
+On the [developer portal](https://www.crunchydata.com/developers/download-postgres/containers), PgBouncer would use this tag:
 
-- `{{< param PGBouncerComponentTagCentos8 >}}`
+- `{{< param PGBouncerComponentTagUbi8 >}}`
 
 PostGIS enabled containers have both the Postgres and PostGIS software versions included. For example, Postgres 14 with PostGIS 3.1 would use the following tags:
 
 - `{{< param postgres14GIS31ComponentTagUbi8 >}}`
 - `{{< param postgres14GIS31TagUbi8 >}}`
-- `{{< param postgres14GIS31ComponentTagCentos8 >}}`
-- `{{< param postgres14GIS31TagCentos8 >}}`
 
 ## Extensions Compatibility
 
diff --git a/docs/content/support/_index.md b/docs/content/support/_index.md
@@ -13,7 +13,7 @@ There are a few options available for community support of the [PGO: the Postgre
 In all cases, please be sure to provide as many details as possible in regards to your issue, including:
 
 - Your Platform (e.g. Kubernetes vX.YY.Z)
-- Operator Version (e.g. {{< param centosBase >}}-{{< param operatorVersion >}})
+- Operator Version (e.g. {{< param operatorVersion >}})
 - A detailed description of the issue, as well as steps you took that lead up to the issue
 - Any relevant logs
 - Any additional information you can provide that you may find helpful
