Pull updates from upstream (mostly repo paths)

Author: josh-heyer

product_docs/docs/postgres_for_kubernetes/1/backup_barmanobjectstore.mdx

@@ -29,7 +29,7 @@ be *tarballs*. Both base backups and WAL files can be compressed
 and encrypted.
 
 For this, it is required to use an image with `barman-cli-cloud` included.
-You can use the image `quay.io/enterprisedb/postgresql` for this scope,
+You can use the image `docker.enterprisedb.com/k8s_enterprise/postgresql` for this scope,
 as it is composed of a community PostgreSQL image and the latest
 `barman-cli-cloud` package.
 

product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx

@@ -641,7 +641,7 @@ metadata:
   name: target-db
 spec:
   instances: 3
-  imageName: quay.io/enterprisedb/postgresql:18.0-system-trixie
+  imageName: docker.enterprisedb.com/k8s_enterprise/postgresql:18.0-system-trixie
 
   bootstrap:
     pg_basebackup:
@@ -691,7 +691,7 @@ metadata:
   name: cluster-clone-tls
 spec:
   instances: 3
-  imageName: quay.io/enterprisedb/postgresql:18.0-system-trixie
+  imageName: docker.enterprisedb.com/k8s_enterprise/postgresql:18.0-system-trixie
 
   bootstrap:
     pg_basebackup:

product_docs/docs/postgres_for_kubernetes/1/container_images.mdx

@@ -39,7 +39,7 @@ automatically overrides it with its instance manager.
 EDB provides and maintains
 [public PostgreSQL container images](https://github.com/enterprisedb/docker-postgres)
 that are fully compatible with {{name.ln}}. These images are published on
-[quay.io](https://quay.io/enterprisedb/postgresql).
+[docker.enterprisedb.com](https://docker.enterprisedb.com/k8s_enterprise/postgresql).
 
 ## Image Tag Requirements
 

product_docs/docs/postgres_for_kubernetes/1/declarative_hibernation.mdx

@@ -55,7 +55,7 @@ $ kubectl cnp status <cluster-name>
 Cluster Summary
 Name:              cluster-example
 Namespace:         default
-PostgreSQL Image:  quay.io/enterprisedb/postgresql:18.0-system-trixie
+PostgreSQL Image:  docker.enterprisedb.com/k8s_enterprise/postgresql:18.0-system-trixie
 Primary instance:  cluster-example-2
 Status:            Cluster in healthy state 
 Instances:         3

product_docs/docs/postgres_for_kubernetes/1/image_catalog.mdx

@@ -35,13 +35,13 @@ metadata:
 spec:
   images:
     - major: 15
-      image: quay.io/enterprisedb/postgresql:15.14-system-trixie
+      image: docker.enterprisedb.com/k8s_enterprise/postgresql:15.14-system-trixie
     - major: 16
-      image: quay.io/enterprisedb/postgresql:16.10-system-trixie
+      image: docker.enterprisedb.com/k8s_enterprise/postgresql:16.10-system-trixie
     - major: 17
-      image: quay.io/enterprisedb/postgresql:17.6-system-trixie
+      image: docker.enterprisedb.com/k8s_enterprise/postgresql:17.6-system-trixie
     - major: 18
-      image: quay.io/enterprisedb/postgresql:18.0-system-trixie
+      image: docker.enterprisedb.com/k8s_enterprise/postgresql:18.0-system-trixie
 ```
 
 **Example of a Cluster-Wide Catalog using `ClusterImageCatalog` Resource:**
@@ -54,13 +54,13 @@ metadata:
 spec:
   images:
     - major: 15
-      image: quay.io/enterprisedb/postgresql:15.14-system-trixie
+      image: docker.enterprisedb.com/k8s_enterprise/postgresql:15.14-system-trixie
     - major: 16
-      image: quay.io/enterprisedb/postgresql:16.10-system-trixie
+      image: docker.enterprisedb.com/k8s_enterprise/postgresql:16.10-system-trixie
     - major: 17
-      image: quay.io/enterprisedb/postgresql:17.6-system-trixie
+      image: docker.enterprisedb.com/k8s_enterprise/postgresql:17.6-system-trixie
     - major: 18
-      image: quay.io/enterprisedb/postgresql:18.0-system-trixie
+      image: docker.enterprisedb.com/k8s_enterprise/postgresql:18.0-system-trixie
 ```
 
 A `Cluster` resource has the flexibility to reference either an `ImageCatalog`

product_docs/docs/postgres_for_kubernetes/1/imagevolume_extensions.mdx

@@ -302,7 +302,7 @@ spec:
 ```
 
 {{name.ln}} will set the `LD_LIBRARY_PATH` environment variable to include
-`/extensions/postgis/system`, allowing PostgreSQL to locate and load these
+`/extensions/postgis/syslib`, allowing PostgreSQL to locate and load these
 system libraries at runtime.
 
 !!! Important

product_docs/docs/postgres_for_kubernetes/1/logical_replication.mdx

@@ -351,7 +351,7 @@ metadata:
 spec:
   instances: 1
 
-  imageName: quay.io/enterprisedb/postgresql:16
+  imageName: docker.enterprisedb.com/k8s_enterprise/postgresql:16
 
   storage:
     size: 1Gi

product_docs/docs/postgres_for_kubernetes/1/pg4k.v1/v1.27.1.mdx

@@ -4137,8 +4137,9 @@ cluster to be reconciled</p>
 <i>bool</i>
 </td>
 <td>
-   <p>Only one plugin can be declared as WALArchiver.
-Cannot be active if &quot;.spec.backup.barmanObjectStore&quot; configuration is present.</p>
+   <p>Marks the plugin as the WAL archiver. At most one plugin can be
+designated as a WAL archiver. This cannot be enabled if the
+<code>.spec.backup.barmanObjectStore</code> configuration is present.</p>
 </td>
 </tr>
 <tr><td><code>parameters</code><br/>

product_docs/docs/postgres_for_kubernetes/1/postgis.mdx

@@ -13,16 +13,20 @@ Systems) objects in the database and be queried via SQL.
     in Kubernetes via {{name.ln}}.
 
 The CloudNativePG Community maintains container images that are built on top
-of the official [PostGIS images hosted on DockerHub](https://hub.docker.com/r/postgis/postgis).
-For more information please visit:
+of the maintained [PostgreSQL Container images](https://github.com/cloudnative-pg/postgres-containers).
+For more information, please visit:
 
 -   The [`postgis-containers` project in GitHub](https://github.com/cloudnative-pg/postgis-containers)
 -   The [`postgis-containers` Container Registry in GitHub](https://github.com/cloudnative-pg/postgis-containers/pkgs/container/postgis)
 
-Additionally, EDB provides container images for EDB Postgres Advanced Server
-that include PostGIS and makes them available in the official
-[registry on Quay.io](https://quay.io/repository/enterprisedb/edb-postgres-advanced?tab=tags)
-with the `-postgis` suffix.
+Additionally, EDB provides container images for:
+
+-   Community PostgreSQL + PostGIS
+-   EDB Postgres Advanced Server (EPAS) + PostGIS
+-   EDB Postgres Extended (PGE) + PostGIS
+
+and makes them available in the official registry
+at `docker.enterprisedb.com`, with the `-postgis` suffix.
 
 ## Basic concepts about a PostGIS cluster
 
@@ -43,18 +47,18 @@ do this in two ways:
 
 -   install it in the application database, which is the main and supposedly only
     database you host in the cluster according to the microservice architecture, or
--   install it in the `template1` database so as to make it available for all the
+-   install it in the `template1` database to make it available for all the
     databases you end up creating in the cluster, in case you adopt the monolith
     architecture where the instance is shared by multiple databases
 
 !!! Info
-    For more information on the microservice vs monolith architecture in the database
+    For more information on the microservice vs monolith architecture in the database,
     please refer to the ["How many databases should be hosted in a single PostgreSQL instance?" FAQ](faq.md)
     or the ["Database import" section](database_import.md).
 
 ## Create a new PostgreSQL cluster with PostGIS
 
-Let's suppose you want to create a new PostgreSQL 14 cluster with PostGIS 3.2.
+Let's suppose you want to create a new PostgreSQL 18 cluster with PostGIS 3.6.
 
 The first step is to ensure you use the right PostGIS container image for the
 operand, and properly set the `.spec.imageName` option in the `Cluster`
@@ -66,82 +70,90 @@ provides some guidance on how the creation of a PostGIS cluster can be done.
 !!! Warning
     Please consider that, although convention over configuration applies in
     {{name.ln}}, you should spend time configuring and tuning your system for
-    production. Also the `imageName` in the example below deliberately points
-    to the latest available image for PostgreSQL 14 - you should use a specific
+    production. Also, the `imageName` in the example below deliberately points
+    to the latest available image for PostgreSQL 17 - you should use a specific
     image name or, preferably, the SHA256 digest for true immutability.
 
 ```yaml
-apiVersion: postgresql.k8s.enterprisedb.io/v1
+apiVersion: postgresql.cnpg.io/v1
 kind: Cluster
 metadata:
   name: postgis-example
 spec:
-  instances: 3
-  imageName: ghcr.io/enterprisedb/postgresql:16-postgis
-  bootstrap:
-    initdb:
-      postInitTemplateSQL:
-        - CREATE EXTENSION postgis;
-        - CREATE EXTENSION postgis_topology;
-        - CREATE EXTENSION fuzzystrmatch;
-        - CREATE EXTENSION postgis_tiger_geocoder;
-
+  instances: 1
+  imageName: docker.enterprisedb.com/k8s_enterprise/postgresql:17-postgis-ubi9
   storage:
     size: 1Gi
+  postgresql:
+    parameters:
+      log_statement: ddl
+---
+apiVersion: postgresql.cnpg.io/v1
+kind: Database
+metadata:
+  name: postgis-example-app
+spec:
+  name: app
+  owner: app
+  cluster:
+    name: postgis-example
+  extensions:
+  - name: postgis
+  - name: postgis_topology
+  - name: fuzzystrmatch
+  - name: postgis_tiger_geocoder
 ```
 
-The example relies on the `postInitTemplateSQL` option which executes a list of
-queries against the `template1` database, before the actual creation of the
-application database (called `app`). This means that, once you have applied the
-manifest and the cluster is up, you will have the above extensions installed in
-both the template database and the application database, ready for use.
+The example leverages the `Database` resource's declarative extension
+management to add the specified extensions to the `app` database.
 
 !!! Info
     Take some time and look at the available options in `.spec.bootstrap.initdb`
     from the [API reference](pg4k.v1.md#postgresql-k8s-enterprisedb-io-v1-BootstrapInitDB), such as
     `postInitApplicationSQL`.
 
+!!! Info
+    For more details, see the
+    ["Managing Extensions in a Database" section](declarative_database_management.md#managing-extensions-in-a-database).
+
 You can easily verify the available version of PostGIS that is in the
 container, by connecting to the `app` database (you might obtain different
 values from the ones in this document):
 
 ```console
-$ kubectl exec -ti postgis-example-1 -- psql app
-Defaulted container "postgres" out of: postgres, bootstrap-controller (init)
-psql (16.0 (Debian 16.0-1.pgdg110+1))
+$ kubectl cnpg psql postgis-example -- app
+psql (18.0 (Debian 18.0-1.pgdg13+3))
 Type "help" for help.
 
 app=# SELECT * FROM pg_available_extensions WHERE name ~ '^postgis' ORDER BY 1;
            name           | default_version | installed_version |                          comment
 --------------------------+-----------------+-------------------+------------------------------------------------------------
- postgis                  | 3.2.2           | 3.2.2             | PostGIS geometry and geography spatial types and functions
- postgis-3                | 3.2.2           |                   | PostGIS geometry and geography spatial types and functions
- postgis_raster           | 3.2.2           |                   | PostGIS raster types and functions
- postgis_raster-3         | 3.2.2           |                   | PostGIS raster types and functions
- postgis_sfcgal           | 3.2.2           |                   | PostGIS SFCGAL functions
- postgis_sfcgal-3         | 3.2.2           |                   | PostGIS SFCGAL functions
- postgis_tiger_geocoder   | 3.2.2           | 3.2.2             | PostGIS tiger geocoder and reverse geocoder
- postgis_tiger_geocoder-3 | 3.2.2           |                   | PostGIS tiger geocoder and reverse geocoder
- postgis_topology         | 3.2.2           | 3.2.2             | PostGIS topology spatial types and functions
- postgis_topology-3       | 3.2.2           |                   | PostGIS topology spatial types and functions
+ postgis                  | 3.6.0           | 3.6.0             | PostGIS geometry and geography spatial types and functions
+ postgis-3                | 3.6.0           |                   | PostGIS geometry and geography spatial types and functions
+ postgis_raster           | 3.6.0           |                   | PostGIS raster types and functions
+ postgis_raster-3         | 3.6.0           |                   | PostGIS raster types and functions
+ postgis_sfcgal           | 3.6.0           |                   | PostGIS SFCGAL functions
+ postgis_sfcgal-3         | 3.6.0           |                   | PostGIS SFCGAL functions
+ postgis_tiger_geocoder   | 3.6.0           | 3.6.0             | PostGIS tiger geocoder and reverse geocoder
+ postgis_tiger_geocoder-3 | 3.6.0           |                   | PostGIS tiger geocoder and reverse geocoder
+ postgis_topology         | 3.6.0           | 3.6.0             | PostGIS topology spatial types and functions
+ postgis_topology-3       | 3.6.0           |                   | PostGIS topology spatial types and functions
 (10 rows)
 ```
 
-The next step is to verify that the extensions listed in the
-`postInitTemplateSQL` section have been correctly installed in the `app`
-database.
+The next step is to verify that the extensions listed in the `Database`
+resource have been correctly installed in the `app` database.
 
 ```console
 app=# \dx
-                                        List of installed extensions
-          Name          | Version |   Schema   |                        Description
-------------------------+---------+------------+------------------------------------------------------------
- fuzzystrmatch          | 1.1     | public     | determine similarities and distance between strings
- plpgsql                | 1.0     | pg_catalog | PL/pgSQL procedural language
- postgis                | 3.2.2   | public     | PostGIS geometry and geography spatial types and functions
- postgis_tiger_geocoder | 3.2.2   | tiger      | PostGIS tiger geocoder and reverse geocoder
- postgis_topology       | 3.2.2   | topology   | PostGIS topology spatial types and functions
-(5 rows)
+                                                 List of installed extensions
+          Name          | Version | Default version |   Schema   |                        Description
+------------------------+---------+-----------------+------------+------------------------------------------------------------
+ fuzzystrmatch          | 1.2     | 1.2             | public     | determine similarities and distance between strings
+ plpgsql                | 1.0     | 1.0             | pg_catalog | PL/pgSQL procedural language
+ postgis                | 3.6.0   | 3.6.0           | public     | PostGIS geometry and geography spatial types and functions
+ postgis_tiger_geocoder | 3.6.0   | 3.6.0           | tiger      | PostGIS tiger geocoder and reverse geocoder
+ postgis_topology       | 3.6.0   | 3.6.0           | topology   | PostGIS topology spatial types and functions
 ```
 
 Finally:
@@ -150,6 +162,7 @@ Finally:
 app=# SELECT postgis_full_version();
                                                                             postgis_full_version
 ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
- POSTGIS="3.2.2 628da50" [EXTENSION] PGSQL="140" GEOS="3.9.0-CAPI-1.16.2" PROJ="7.2.1" LIBXML="2.9.10" LIBJSON="0.15" LIBPROTOBUF="1.3.3" WAGYU="0.5.0 (Internal)" TOPOLOGY
+ POSTGIS="3.6.0 4c1967d" [EXTENSION] PGSQL="180" GEOS="3.13.1-CAPI-1.19.2" PROJ="9.6.0 NETWORK_ENABLED=OFF URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/tmp/proj DATABASE_PATH=/usr/share/proj/proj.
+db" (compiled against PROJ 9.6.0) LIBXML="2.9.14" LIBJSON="0.18" LIBPROTOBUF="1.5.1" WAGYU="0.5.0 (Internal)" TOPOLOGY
 (1 row)
 ```

product_docs/docs/postgres_for_kubernetes/1/postgres_upgrades.mdx

@@ -154,7 +154,7 @@ kind: Cluster
 metadata:
   name: cluster-example
 spec:
-  imageName: quay.io/enterprisedb/postgresql:16-minimal-trixie
+  imageName: docker.enterprisedb.com/k8s_enterprise/postgresql:16-minimal-trixie
   instances: 3
   storage:
     size: 1Gi
@@ -181,7 +181,7 @@ kind: Cluster
 metadata:
   name: cluster-example
 spec:
-  imageName: quay.io/enterprisedb/postgresql:17-minimal-trixie
+  imageName: docker.enterprisedb.com/k8s_enterprise/postgresql:17-minimal-trixie
   instances: 3
   storage:
     size: 1Gi