docs: import CloudNativePG

Author: github-actions

docs/declarative_database_management.md

@@ -402,12 +402,8 @@ Each foreign server entry supports the following properties:
     - `ensure`: Indicates whether the option should be `present` or `absent`.
 
 :::info[Important]
-:::
-
-The `fdw` field must reference an existing foreign data wrapper already defined in the database.
-If the specified FDW does not exist, the foreign server will not be created.
-
-:::info
+    The `fdw` field must reference an existing foreign data wrapper already defined in the database.
+    If the specified FDW does not exist, the foreign server will not be created.
 :::
 
 CloudNativePG manages foreign servers using PostgreSQL’s native SQL commands:

docs/preview_version.md

@@ -12,9 +12,9 @@ testing before the community issues a new generally available (GA) release.
 These versions are feature-frozen, meaning no new features are added, and are
 intended for public testing prior to the final release.
 
-:::info[Important]
-    CloudNativePG release candidates are not intended for use in production
-    systems.
+:::warning[Important]
+    CloudNativePG release candidates are **not intended for use in production** systems.
+    They should only be deployed in staging or dedicated testing environments.
 :::
 
 ## Purpose of Release Candidates
@@ -24,13 +24,47 @@ the official release. While a release candidate aims to be identical to the
 initial release of a new minor version of CloudNativePG, additional changes may
 be implemented before the GA release.
 
-## Community Involvement
+### Mitigating Critical Issues
+
+The primary purpose of an RC is to catch serious defects and regressions that our
+automated testing and internal manual checks might miss. **Specifically, community testing
+is invaluable for validating real-world scenarios, such as:**
+
+- **Upgrade Paths:** Testing the process of upgrading an existing CloudNativePG
+  cluster from the previous stable minor version to the RC version. This often
+  uncovers critical compatibility or migration issues, like those that affect PVC
+  ownership, which can only be reliably tested with diverse existing user setups.
+- **Unique Configurations:** Validating compatibility with specific Kubernetes
+  versions, storage providers, networking setups, or custom PostgreSQL
+  extensions not covered by our standard test matrix.
+- **Real-world Workloads:** Running the RC with your actual application
+  workload and traffic patterns to expose performance regressions or race
+  conditions.
+
+## Community Involvement: How to Help
 
 The stability of each CloudNativePG minor release significantly depends on the
 community's efforts to test the upcoming version with their workloads and
 tools. Identifying bugs and regressions through user testing is crucial in
 determining when we can finalize the release.
 
+### Your Call to Action
+
+If a Release Candidate is available, we encourage you to perform the following tests in a
+non-production environment:
+
+- **New Deployment Test:** Deploy a new CloudNativePG cluster using the RC version.
+- **Upgrade Test (Crucial):** **Upgrade an existing cluster** (from the
+  preceding stable minor version) to the RC version, and verify all key
+  operational aspects (scaling, failover, backup/restore) function correctly.
+- **Basic Operations:** Verify key features like rolling update,
+  backup/restore, instance failover, and connection pooling function as
+  expected.
+- **Report Issues:** **Immediately report any issues or unexpected behavior**
+  by opening a GitHub issue and clearly marking it with a **`Release
+  Candidate`** tag or label, along with the RC version number
+  (e.g., `1.28.0-rc1`).
+
 ## Usage Advisory
 
 The CloudNativePG Community strongly advises against using preview versions of
@@ -39,6 +73,9 @@ CloudNativePG undergoes extensive automated and manual testing, beta releases
 may contain serious bugs. Features in preview versions may change in ways that
 are not backwards compatible and could be removed entirely.
 
+**By testing the Release Candidate, you are helping to prevent a potentially
+critical bug from affecting the entire community upon the GA release.**
+
 ## Current Preview Version
 
 There are currently no preview versions available.

docs/release_notes/v1.28.md

@@ -47,9 +47,10 @@ on the release branch in GitHub.
 - Enabled simultaneous image and configuration changes when using
   `primaryUpdateMethod: restart`, allowing you to update the container image
   (including PostgreSQL version or extensions) and PostgreSQL configuration
-  settings in the same operation. Note that when using `primaryUpdateMethod:
-  switchover`, image and configuration changes must still be performed
-  separately to avoid configuration mismatches during the switchover process.
+  settings in the same operation.
+  Note that when using `primaryUpdateMethod: switchover`, image and
+  configuration changes must still be performed separately to avoid configuration
+  mismatches during the switchover process.
   ([#8241](https://github.com/cloudnative-pg/cloudnative-pg/pull/8241))
 
 - Improved network failure detection for replica instances by setting the

docs/security.md

@@ -495,18 +495,16 @@ You can assign an
 [AppArmor](https://kubernetes.io/docs/tutorials/security/apparmor/) profile to
 the `postgres`, `initdb`, `join`, `full-recovery` and `bootstrap-controller` containers inside every `Cluster` pod through the
 `container.apparmor.security.beta.kubernetes.io` annotation.
+For example:
 
-:::note[Example of cluster annotations]
-:::
-
-```
-	kind: Cluster
-	metadata:
-		name: cluster-apparmor
-		annotations:
-			container.apparmor.security.beta.kubernetes.io/postgres: runtime/default
-			container.apparmor.security.beta.kubernetes.io/initdb: runtime/default
-			container.apparmor.security.beta.kubernetes.io/join: runtime/default
+```yaml
+kind: Cluster
+metadata:
+  name: cluster-apparmor
+  annotations:
+    container.apparmor.security.beta.kubernetes.io/postgres: runtime/default
+    container.apparmor.security.beta.kubernetes.io/initdb: runtime/default
+    container.apparmor.security.beta.kubernetes.io/join: runtime/default
 ```
 
 :::warning