CloudNativePG

We want to expand the scope of the CloudNativePG tests, introducing a full-fledged chaos testing framework that can be used to better validate the resilience, fault tolerance and recovery mechanisms of CloudNativePG. Expected Outcome: 1. Selection of a Kubernetes-native chaos testing framework (e.g., LitmusChaos or Chaos Mesh). 2. Design and automation of an initial set of chaos experiments covering common failure scenarios. 3. Integration of these experiments into CI/CD to ensure reproducible testing. 4. Collection of clear observability metrics (e.g., failover time, data consistency) to assess resilience and recovery. 5. Documentation and guidelines to help contributors create and run new chaos experiments safely.

The current documentation of CloudNativePG (a Kubernetes-native Postgres operator) is statically built using mkdocs from Markdown sources, which must live with the rest of the source code as they are part of it. We want to modernise this process and introduce multi-version support, helping users find accurate information for the version they are running in production. This project aims to rebuild the documentation site using Docusaurus (preferred) or an equivalent static site generator to enable multi-version documentation and version selection. Additionally, any initiatives that improve content structure, navigation, searchability, and clarity are welcome, provided they enhance logical flow and maintainability while aligning with CNCF and user expectations. The documentation is hosted on GitHub Pages under the CloudNativePG website domain. Expected Outcome: 1. Incremental set of pull requests (PRs) with: a. Site built with Docusaurus (or equivalent) with version selector working. b. Content restructured for clarity and easier navigation. c. Clean, consistent navigation structure and enhanced search capabilities. d. Staging website capabilities. e. Deployment workflow to GitHub Pages using Dagger and GitHub Actions. 2. A clear contributor guide explaining how maintainers can add or update documentation for each version in the future.

This project aims to extend the CloudNativePG operator to support declarative configuration of foreign data wrappers through its Database custom resource. PostgreSQL supports the SQL/MED (Management of External Data) specification, enabling access to external data sources through standard SQL queries. These sources—known as foreign data—are accessed via foreign data wrappers (FDWs), which are libraries that handle the connection and data exchange with the external systems. A variety of FDWs are available for PostgreSQL. Of particular interest for this project is the postgres_fdw extension, which facilitates access to other PostgreSQL instances. Expected Outcome: 1) A detailed design discussion documented in the upstream issue in CloudNativePG GitHub repository, involving mentors, maintainers, and the community. 2) A fully working pull request implementing support for declarative foreign data wrappers, complete with: a. Reconciliation logic for the Database resource controller b. Documentation c. Automated tests integrated into the CI/CD pipeline