docs: import CloudNativePG main

Author: cnpg-bot

website/docs/cloudnative-pg.v1.md

@@ -275,8 +275,10 @@ _Appears in:_
 | `backupId` _string_ | The ID of the Barman backup |  |  |  |
 | `backupName` _string_ | The Name of the Barman backup |  |  |  |
 | `phase` _[BackupPhase](#backupphase)_ | The last backup status |  |  |  |
-| `startedAt` _[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)_ | When the backup was started |  |  |  |
-| `stoppedAt` _[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)_ | When the backup was terminated |  |  |  |
+| `startedAt` _[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)_ | When the backup execution was started by the backup tool |  |  |  |
+| `stoppedAt` _[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)_ | When the backup execution was terminated by the backup tool |  |  |  |
+| `reconciliationStartedAt` _[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)_ | When the backup process was started by the operator |  |  |  |
+| `reconciliationTerminatedAt` _[Time](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.34/#time-v1-meta)_ | When the reconciliation was terminated by the operator (either successfully or not) |  |  |  |
 | `beginWal` _string_ | The starting WAL |  |  |  |
 | `endWal` _string_ | The ending WAL |  |  |  |
 | `beginLSN` _string_ | The starting xlog |  |  |  |
@@ -2230,7 +2232,7 @@ _Appears in:_
 | `targetXID` _string_ | The target transaction ID |  |  |  |
 | `targetName` _string_ | The target name (to be previously created<br />with `pg_create_restore_point`) |  |  |  |
 | `targetLSN` _string_ | The target LSN (Log Sequence Number) |  |  |  |
-| `targetTime` _string_ | The target time as a timestamp in the RFC3339 standard |  |  |  |
+| `targetTime` _string_ | The target time as a timestamp in RFC3339 format or PostgreSQL timestamp format.<br />Timestamps without an explicit timezone are interpreted as UTC. |  |  |  |
 | `targetImmediate` _boolean_ | End recovery as soon as a consistent state is reached |  |  |  |
 | `exclusive` _boolean_ | Set the target to be exclusive. If omitted, defaults to false, so that<br />in Postgres, `recovery_target_inclusive` will be true |  |  |  |
 

website/docs/connection_pooling.md

@@ -221,15 +221,38 @@ replicate similar behavior to the default setup.
 
 ## Pod templates
 
-You can take advantage of pod templates specification in the `template`
-section of a `Pooler` resource. For details, see
-[`PoolerSpec`](cloudnative-pg.v1.md#poolerspec) in the API reference.
 
-Using templates, you can configure pods as you like, including fine control
-over affinity and anti-affinity rules for pods and nodes. By default,
-containers use images from `ghcr.io/cloudnative-pg/pgbouncer`.
+The `Pooler` resource allows you to customize the underlying pods via the
+`template` section. This provides full access to the Kubernetes `PodSpec` for
+advanced configurations like scheduling constraints, custom security contexts,
+or resource overrides.
 
-This example shows `Pooler` specifying `PodAntiAffinity``:
+For a complete list of supported fields, see the
+[`PoolerSpec`](cloudnative-pg.v1.md#poolerspec) API reference.
+
+### Key requirements
+
+- **The `pgbouncer` container name:** When overriding container settings (like
+  images or resources), the name of the container **must** be set to
+  `pgbouncer`. The operator looks for this specific name to manage the
+  PgBouncer process.
+
+- **Mandatory `containers` field:** Since `template` follows the standard
+  Kubernetes `PodSpec` schema, the `containers` field is mandatory.
+
+- If you aren't modifying container-level settings, you must set it to an empty
+  array: `containers: []`.
+
+- If the `containers` field is missing, the API server will throw a
+  `ValidationError`.
+
+### Examples
+
+#### High availability with pod anti-affinity
+
+This configuration uses `podAntiAffinity` to ensure that PgBouncer pods are
+distributed across different nodes, preventing a single node failure from
+taking down the entire pool.
 
 ```yaml
 apiVersion: postgresql.cnpg.io/v1
@@ -260,16 +283,10 @@ spec:
             topologyKey: "kubernetes.io/hostname"
 ```
 
-:::note
-    Explicitly set `.spec.template.spec.containers` to `[]` when not modified,
-    as it's a required field for a `PodSpec`. If `.spec.template.spec.containers`
-    isn't set, the Kubernetes api-server returns the following error when trying to
-    apply the manifest:`error validating "pooler.yaml": error validating data:
-    ValidationError(Pooler.spec.template.spec): missing required field
-    "containers"`
-:::
+#### Custom image and resource limits
 
-This example sets resources and changes the used image:
+You can specify a custom image and define resource requests/limits. Note that
+the container name is explicitly set to `pgbouncer`.
 
 ```yaml
 apiVersion: postgresql.cnpg.io/v1
@@ -288,6 +305,7 @@ spec:
         app: pooler
     spec:
       containers:
+        # This name MUST be "pgbouncer"
         - name: pgbouncer
           image: my-pgbouncer:latest
           resources:

website/docs/recovery.md

@@ -367,7 +367,7 @@ spec:
           kind: VolumeSnapshot
           apiGroup: snapshot.storage.k8s.io
       recoveryTarget:
-        targetTime: "2023-07-06T08:00:39"
+        targetTime: "2023-07-06T08:00:39Z"
   externalClusters:
     - name: origin
       plugin:
@@ -405,9 +405,21 @@ Here are the recovery target criteria you can use:
 
 targetTime
 :  Time stamp up to which recovery proceeds, expressed in
-   [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) format.
+   [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339) format, or as a
+   [timestamp](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-RECOVERY-TARGET-TIME).
    (The precise stopping point is also influenced by the `exclusive` option.)
 
+:::note
+    Timestamps without an explicit timezone suffix
+    (e.g., `2023-07-06 08:00:39`) are interpreted as UTC.
+:::
+
+:::warning
+    Always specify an explicit timezone in your timestamp to avoid ambiguity.
+    For example, use `2023-07-06T08:00:39Z` or `2023-07-06T08:00:39+02:00`
+    instead of `2023-07-06 08:00:39`.
+:::
+
 :::warning
     PostgreSQL recovery will stop when it encounters the first transaction that
     occurs after the specified time. If no such transaction exists after the
@@ -623,4 +635,4 @@ data.
     cluster. However, this is strongly discouraged unless you are highly
     familiar with PostgreSQL's recovery process. Skipping the check incorrectly can
     lead to severe data loss. Use with caution and only in expert scenarios.
-:::
+:::