Merge pull request #4533 from EnterpriseDB/automatic_docs_update/repo…

…_EnterpriseDB/cloud-native-postgres/ref_refs/tags/v1.20.2

Process changes to docs from: repo: EnterpriseDB/cloud-native-postgres ref: refs/tags/v1.20.2

product_docs/docs/postgres_for_kubernetes/1/api_reference.mdx

@@ -892,7 +892,7 @@ RecoveryTarget allows to configure the moment where the recovery process will st
 | `targetLSN      ` | The target LSN (Log Sequence Number)                                                                                                                                                                                                                 | string |
 | `targetTime     ` | The target time as a timestamp in the RFC3339 standard                                                                                                                                                                                               | string |
 | `targetImmediate` | End recovery as soon as a consistent state is reached                                                                                                                                                                                                | \*bool |
-| `exclusive      ` | Set the target to be exclusive (defaults to true)                                                                                                                                                                                                    | \*bool |
+| `exclusive      ` | Set the target to be exclusive. If omitted, defaults to false, so that in Postgres, `recovery_target_inclusive` will be true                                                                                                                         | \*bool |
 
 <a id='ReplicaClusterConfiguration'></a>
 

product_docs/docs/postgres_for_kubernetes/1/bootstrap.mdx

@@ -702,10 +702,11 @@ You can choose only a single one among the targets above in each
 Additionally, you can specify `targetTLI` force recovery to a specific
 timeline.
 
-By default, the previous parameters are considered to be exclusive, stopping
-just before the recovery target. You can request inclusive behavior,
-stopping right after the recovery target, setting the `exclusive` parameter to
-`false` like in the following example relying on a blob container in Azure:
+By default, the previous parameters are considered to be inclusive, stopping
+just after the recovery target, matching [the behavior in PostgreSQL](https://www.postgresql.org/docs/current/runtime-config-wal.html#GUC-RECOVERY-TARGET-INCLUSIVE)
+You can request exclusive behavior,
+stopping right before the recovery target, by setting the `exclusive` parameter to
+`true` like in the following example relying on a blob container in Azure:
 
 ```yaml
 apiVersion: postgresql.k8s.enterprisedb.io/v1
@@ -724,7 +725,7 @@ spec:
       recoveryTarget:
         backupID: 20220616T142236
         targetName: "maintenance-activity"
-        exclusive: false
+        exclusive: true
 
   externalClusters:
     - name: clusterBackup

product_docs/docs/postgres_for_kubernetes/1/index.mdx

@@ -67,7 +67,6 @@ full lifecycle of a highly available Postgres database clusters with a
 primary/standby architecture, using native streaming replication.
 
 !!! Note
-
     The operator has been renamed from Cloud Native PostgreSQL. Existing users
     of Cloud Native PostgreSQL will not experience any change, as the underlying
     components and resources have not changed.
@@ -90,7 +89,7 @@ primary/standby architecture, using native streaming replication.
 
 ## Features unique to EDB Postgres of Kubernetes
 
--   Long Term Support for 1.18.x
+-   [Long Term Support](#long-term-support) for 1.18.x
 -   Red Hat certified operator for OpenShift
 -   Support on IBM Power
 -   EDB Postgres for Kubernetes Plugin
@@ -102,11 +101,26 @@ You can [evaluate EDB Postgres for Kubernetes for free](evaluation.md).
 You need a valid license key to use EDB Postgres for Kubernetes in production.
 
 !!! Note
-
     Based on the [Operator Capability Levels model](operator_capability_levels.md),
     users can expect a **"Level V - Auto Pilot"** set of capabilities from the
     EDB Postgres for Kubernetes Operator.
 
+### Long Term Support
+
+EDB is committed to declaring one version of EDB Postgres for Kubernetes per
+year as a Long Term Support version. This version will be supported and receive
+maintenance releases for an additional 12 months beyond the last release of
+CloudNativePG by the community for the same version. For example, the last
+version of 1.18 of CloudNativePG was released on June 12, 2023.  This was
+declared a LTS version of EDB Postgres for Kubernetes and it will be supported
+for additional 12 months until June 12, 2024.  Customers can expect that they
+will have at least 6 months to move between LTS versions. So they should
+expect the next LTS to be available by January 12, 2024 to allow at least 6
+months to migrate. While we encourage customers to regularly upgrade to the
+latest version of the operator to take advantage of new features, having LTS
+versions allows customers desiring additional stability to stay on the same
+version for 12-18 months before upgrading.
+
 ## Licensing
 
 EDB Postgres for Kubernetes works with both PostgreSQL and EDB Postgres
@@ -130,7 +144,6 @@ The EDB Postgres for Kubernetes Operator container images support the multi-arch
 format for the following platforms: `linux/amd64`, `linux/arm64`, `linux/ppc64le`, `linux/s390x`.
 
 !!! Warning
-
     EDB Postgres for Kubernetes requires that all nodes in a Kubernetes cluster have the
     same CPU architecture, thus a hybrid CPU architecture Kubernetes cluster is not
     supported. Additionally, EDB supports `linux/ppc64le` and `linux/s390x` architectures
@@ -156,7 +169,6 @@ In case you are not familiar with some basic terminology on Kubernetes and Postg
 please consult the ["Before you start" section](before_you_start.md).
 
 !!! Note
-
     Although the guide primarily addresses Kubernetes, all concepts can
     be extended to OpenShift as well.
 

product_docs/docs/postgres_for_kubernetes/1/installation_upgrade.mdx

@@ -19,12 +19,12 @@ The operator can be installed using the provided [Helm chart](https://github.com
 The operator can be installed like any other resource in Kubernetes,
 through a YAML manifest applied via `kubectl`.
 
-You can install the [latest operator manifest](https://get.enterprisedb.io/cnp/postgresql-operator-1.20.1.yaml)
+You can install the [latest operator manifest](https://get.enterprisedb.io/cnp/postgresql-operator-1.20.2.yaml)
 for this minor release as follows:
 
 ```sh
 kubectl apply -f \
-  https://get.enterprisedb.io/cnp/postgresql-operator-1.20.1.yaml
+  https://get.enterprisedb.io/cnp/postgresql-operator-1.20.2.yaml
 ```
 
 You can verify that with: