Skip to content

Commit a3db567

Browse files
cnpg-botcnpg-bot
committed
docs: import CloudNativePG main
1 parent 7a69e6a commit a3db567

File tree

10 files changed

+301
-87
lines changed

10 files changed

+301
-87
lines changed

‎website/docs/image_catalog.md‎

Lines changed: 14 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -142,15 +142,23 @@ instructions on how to select or override catalog extensions within a cluster.
142142

143143
## CloudNativePG Catalogs
144144

145+
145146
The CloudNativePG project maintains `ClusterImageCatalog` manifests for all
146147
supported images.
147148

148-
These catalogs are regularly updated and published in the
149-
[artifacts repository](https://github.com/cloudnative-pg/artifacts/tree/main/image-catalogs).
149+
These catalogs are regularly updated and published in two distinct locations
150+
within the [artifacts repository](https://github.com/cloudnative-pg/artifacts/tree/main):
151+
152+
- **[`image-catalogs`](https://github.com/cloudnative-pg/artifacts/tree/main/image-catalogs):**
153+
core catalog definitions for base image types.
154+
155+
- **[`image-catalogs-extensions`](https://github.com/cloudnative-pg/artifacts/tree/main/image-catalogs-extensions):**
156+
identical to the above catalogs, with the key difference that the `minimal`
157+
image type includes extension definitions.
150158

151-
Each catalog corresponds to a specific combination of image type (e.g.
152-
`minimal`) and Debian release (e.g. `trixie`). It lists the most up-to-date
153-
container images for every supported PostgreSQL major version.
159+
Each catalog corresponds to a specific combination of image type and Debian
160+
release (e.g., `trixie`). It lists the most up-to-date container images for
161+
every supported PostgreSQL major version.
154162

155163
:::important
156164
To ensure maximum security and immutability, all images within official
@@ -160,7 +168,7 @@ just tags.
160168

161169
### Version Compatibility
162170

163-
While standard catalogs work with older versions of the operator, **catalogs
171+
While core catalogs work with older versions of the operator, **catalogs
164172
containing an `extensions` section are only compatible with CloudNativePG 1.29
165173
or later**. Using a catalog with extension definitions on an older operator
166174
will result in those definitions being rejected.

‎website/docs/installation_upgrade.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,12 +14,12 @@ title: Installation and upgrades
1414
The operator can be installed like any other resource in Kubernetes,
1515
through a YAML manifest applied via `kubectl`.
1616

17-
You can install the [latest operator manifest](https://raw.githubusercontent.com/cloudnative-pg/cloudnative-pg/release-1.28/releases/cnpg-1.28.1.yaml)
17+
You can install the [latest operator manifest](https://raw.githubusercontent.com/cloudnative-pg/cloudnative-pg/main/releases/cnpg-1.29.0-rc1.yaml)
1818
for this minor release as follows:
1919

2020
```sh
2121
kubectl apply --server-side -f \
22-
https://raw.githubusercontent.com/cloudnative-pg/cloudnative-pg/release-1.28/releases/cnpg-1.28.1.yaml
22+
https://raw.githubusercontent.com/cloudnative-pg/cloudnative-pg/main/releases/cnpg-1.29.0-rc1.yaml
2323
```
2424

2525
You can verify that with:
@@ -81,7 +81,7 @@ specific minor release, you can just run:
8181

8282
```sh
8383
curl -sSfL \
84-
https://raw.githubusercontent.com/cloudnative-pg/artifacts/release-1.28/manifests/operator-manifest.yaml | \
84+
https://raw.githubusercontent.com/cloudnative-pg/artifacts/release-1.29/manifests/operator-manifest.yaml | \
8585
kubectl apply --server-side -f -
8686
```
8787

‎website/docs/kubectl-plugin.md‎

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -38,11 +38,11 @@ them in your systems.
3838

3939
#### Debian packages
4040

41-
For example, let's install the 1.28.1 release of the plugin, for an Intel based
41+
For example, let's install the 1.29.0-rc1 release of the plugin, for an Intel based
4242
64 bit server. First, we download the right `.deb` file.
4343

4444
```sh
45-
wget https://github.com/cloudnative-pg/cloudnative-pg/releases/download/v1.28.1/kubectl-cnpg_1.28.1_linux_x86_64.deb \
45+
wget https://github.com/cloudnative-pg/cloudnative-pg/releases/download/v1.29.0-rc1/kubectl-cnpg_1.29.0-rc1_linux_x86_64.deb \
4646
--output-document kube-plugin.deb
4747
```
4848

@@ -53,17 +53,17 @@ $ sudo dpkg -i kube-plugin.deb
5353
Selecting previously unselected package cnpg.
5454
(Reading database ... 6688 files and directories currently installed.)
5555
Preparing to unpack kube-plugin.deb ...
56-
Unpacking cnpg (1.28.1) ...
57-
Setting up cnpg (1.28.1) ...
56+
Unpacking cnpg (1.29.0-rc1) ...
57+
Setting up cnpg (1.29.0-rc1) ...
5858
```
5959

6060
#### RPM packages
6161

62-
As in the example for `.rpm` packages, let's install the 1.28.1 release for an
62+
As in the example for `.rpm` packages, let's install the 1.29.0-rc1 release for an
6363
Intel 64 bit machine. Note the `--output` flag to provide a file name.
6464

6565
```sh
66-
curl -L https://github.com/cloudnative-pg/cloudnative-pg/releases/download/v1.28.1/kubectl-cnpg_1.28.1_linux_x86_64.rpm \
66+
curl -L https://github.com/cloudnative-pg/cloudnative-pg/releases/download/v1.29.0-rc1/kubectl-cnpg_1.29.0-rc1_linux_x86_64.rpm \
6767
--output kube-plugin.rpm
6868
```
6969

@@ -77,7 +77,7 @@ Dependencies resolved.
7777
Package Architecture Version Repository Size
7878
====================================================================================================
7979
Installing:
80-
cnpg x86_64 1.28.1-1 @commandline 20 M
80+
cnpg x86_64 1.29.0-rc1-1 @commandline 20 M
8181

8282
Transaction Summary
8383
====================================================================================================
@@ -306,9 +306,9 @@ sandbox-3 0/604DE38 0/604DE38 0/604DE38 0/604DE38 00:00:00 00:00:00 00
306306
Instances status
307307
Name Current LSN Replication role Status QoS Manager Version Node
308308
---- ----------- ---------------- ------ --- --------------- ----
309-
sandbox-1 0/604DE38 Primary OK BestEffort 1.28.1 k8s-eu-worker
310-
sandbox-2 0/604DE38 Standby (async) OK BestEffort 1.28.1 k8s-eu-worker2
311-
sandbox-3 0/604DE38 Standby (async) OK BestEffort 1.28.1 k8s-eu-worker
309+
sandbox-1 0/604DE38 Primary OK BestEffort 1.29.0-rc1 k8s-eu-worker
310+
sandbox-2 0/604DE38 Standby (async) OK BestEffort 1.29.0-rc1 k8s-eu-worker2
311+
sandbox-3 0/604DE38 Standby (async) OK BestEffort 1.29.0-rc1 k8s-eu-worker
312312
```
313313

314314
If you require more detailed status information, use the `--verbose` option (or
@@ -362,9 +362,9 @@ sandbox-primary primary 1 1 1
362362
Instances status
363363
Name Current LSN Replication role Status QoS Manager Version Node
364364
---- ----------- ---------------- ------ --- --------------- ----
365-
sandbox-1 0/6053720 Primary OK BestEffort 1.28.1 k8s-eu-worker
366-
sandbox-2 0/6053720 Standby (async) OK BestEffort 1.28.1 k8s-eu-worker2
367-
sandbox-3 0/6053720 Standby (async) OK BestEffort 1.28.1 k8s-eu-worker
365+
sandbox-1 0/6053720 Primary OK BestEffort 1.29.0-rc1 k8s-eu-worker
366+
sandbox-2 0/6053720 Standby (async) OK BestEffort 1.29.0-rc1 k8s-eu-worker2
367+
sandbox-3 0/6053720 Standby (async) OK BestEffort 1.29.0-rc1 k8s-eu-worker
368368
```
369369

370370
With an additional `-v` (e.g. `kubectl cnpg status sandbox -v -v`), you can
@@ -640,12 +640,12 @@ Archive: report_operator_<TIMESTAMP>.zip
640640

641641
```output
642642
====== Beginning of Previous Log =====
643-
2023-03-28T12:56:41.251711811Z {"level":"info","ts":"2023-03-28T12:56:41Z","logger":"setup","msg":"Starting CloudNativePG Operator","version":"1.28.1","build":{"Version":"1.28.1+dev107","Commit":"cc9bab17","Date":"2023-03-28"}}
643+
2023-03-28T12:56:41.251711811Z {"level":"info","ts":"2023-03-28T12:56:41Z","logger":"setup","msg":"Starting CloudNativePG Operator","version":"1.29.0-rc1","build":{"Version":"1.29.0-rc1+dev107","Commit":"cc9bab17","Date":"2023-03-28"}}
644644
2023-03-28T12:56:41.251851909Z {"level":"info","ts":"2023-03-28T12:56:41Z","logger":"setup","msg":"Starting pprof HTTP server","addr":"0.0.0.0:6060"}
645645
<snipped …>
646646
647647
====== End of Previous Log =====
648-
2023-03-28T12:57:09.854306024Z {"level":"info","ts":"2023-03-28T12:57:09Z","logger":"setup","msg":"Starting CloudNativePG Operator","version":"1.28.1","build":{"Version":"1.28.1+dev107","Commit":"cc9bab17","Date":"2023-03-28"}}
648+
2023-03-28T12:57:09.854306024Z {"level":"info","ts":"2023-03-28T12:57:09Z","logger":"setup","msg":"Starting CloudNativePG Operator","version":"1.29.0-rc1","build":{"Version":"1.29.0-rc1+dev107","Commit":"cc9bab17","Date":"2023-03-28"}}
649649
2023-03-28T12:57:09.854363943Z {"level":"info","ts":"2023-03-28T12:57:09Z","logger":"setup","msg":"Starting pprof HTTP server","addr":"0.0.0.0:6060"}
650650
```
651651

‎website/docs/operator_capability_levels.md‎

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -52,12 +52,18 @@ that defines four major `CustomResourceDefinition` objects: `Cluster`, `Pooler`,
5252
### PostgreSQL cluster deployment via declarative configuration
5353

5454
You define a PostgreSQL cluster (operand) using the `Cluster` custom resource
55-
in a fully declarative way. The PostgreSQL version is determined by the
56-
operand container image defined in the CR, which is automatically fetched
57-
from the requested registry. When deploying an operand, the operator also
58-
creates the following resources: `Pod`, `Service`, `Secret`,
59-
`ConfigMap`,`PersistentVolumeClaim`, `PodDisruptionBudget`, `ServiceAccount`,
60-
`RoleBinding`, and `Role`.
55+
in a fully declarative way. The PostgreSQL version is determined by the operand
56+
container image defined in the CR, which is automatically fetched from the
57+
requested registry.
58+
When deploying an operand, the operator also creates the following resources:
59+
`Pod`, `Service`, `Secret`, `ConfigMap`, `PersistentVolumeClaim`,
60+
`PodDisruptionBudget`, `ServiceAccount`, `RoleBinding`, and `Role`.
61+
62+
You can optionally provide a pre-existing ServiceAccount for both `Cluster` and
63+
`Pooler` resources. This shared ServiceAccount support enables seamless
64+
integration with cloud-native identity providers allowing you to manage IAM
65+
roles and permissions at the infrastructure level rather than on a per-cluster
66+
basis.
6167

6268
### Override of operand images through the CRD
6369

‎website/docs/preview_version.md‎

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,19 @@ intended for public testing prior to the final release.
1717
They should only be deployed in staging or dedicated testing environments.
1818
:::
1919

20+
21+
## Current Preview Version
22+
23+
<!--
24+
There are currently no preview versions available.
25+
-->
26+
The current preview version is **1.29.0-rc1**.
27+
28+
For more information on the current preview version and how to test, please view the links below:
29+
30+
- [Announcement](https://cloudnative-pg.io/releases/cloudnative-pg-1-29.0-rc1-released/)
31+
- [Documentation](https://cloudnative-pg.io/docs/preview/)
32+
2033
## Purpose of Release Candidates
2134

2235
Release candidates are provided to the community for extensive testing before
@@ -63,7 +76,7 @@ non-production environment:
6376
- **Report Issues:** **Immediately report any issues or unexpected behavior**
6477
by opening a GitHub issue and clearly marking it with a **`Release
6578
Candidate`** tag or label, along with the RC version number
66-
(e.g., `1.28.0-rc1`).
79+
(e.g., `1.29.0-rc1`).
6780

6881
## Usage Advisory
6982

@@ -75,16 +88,3 @@ are not backwards compatible and could be removed entirely.
7588

7689
**By testing the Release Candidate, you are helping to prevent a potentially
7790
critical bug from affecting the entire community upon the GA release.**
78-
79-
## Current Preview Version
80-
81-
There are currently no preview versions available.
82-
83-
<!--
84-
The current preview version is **1.29.0-rc1**.
85-
86-
For more information on the current preview version and how to test, please view the links below:
87-
88-
- [Announcement](https://cloudnative-pg.io/releases/cloudnative-pg-1-29.0-rc1-released/)
89-
- [Documentation](https://cloudnative-pg.io/documentation/preview/)
90-
-->

‎website/docs/release_notes.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ title: Release notes
99

1010
History of user-visible changes for CloudNativePG, classified for each minor release.
1111

12-
<!-- - [CloudNativePG 1.29 - Release Candidate](release_notes/v1.29.md) -->
12+
- [CloudNativePG 1.29 - Release Candidate](release_notes/v1.29.md) (preview)
1313
- [CloudNativePG 1.28](release_notes/v1.28.md)
1414
- [CloudNativePG 1.27](release_notes/v1.27.md)
1515

‎website/docs/release_notes/v1.28.md‎

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -11,26 +11,6 @@ For a complete list of changes, please refer to the
1111
[commits](https://github.com/cloudnative-pg/cloudnative-pg/commits/release-1.28)
1212
on the release branch in GitHub.
1313

14-
<!-- Rolling over (for 1.29.0)
15-
- Introduced a "Terminal Error" phase for backups that encounter unrecoverable
16-
issues (such as invalid credentials or non-existent cloud buckets).
17-
This ensures the operator stops retrying doomed operations, preventing
18-
resource exhaustion and providing immediate, clear feedback in the status.
19-
([#9353](https://github.com/cloudnative-pg/cloudnative-pg/pull/9353))
20-
21-
- Improved monitoring of long-running backups by introducing
22-
`reconciliationStartedAt` and `reconciliationTerminatedAt` fields to the
23-
`Backup` status. This change separates the operator's internal lifecycle from
24-
the actual backup tool's execution timing (`startedAt`/`stoppedAt`), allowing
25-
users to track when the operator begins processing a request.
26-
([#9351](https://github.com/cloudnative-pg/cloudnative-pg/pull/9351))
27-
28-
- Added a `Pending` phase to the `Backup` status to explicitly indicate when a
29-
backup is queued and waiting for an available worker or instance
30-
availability.
31-
([#9364](https://github.com/cloudnative-pg/cloudnative-pg/pull/9364))
32-
-->
33-
3414
## Version 1.28.1
3515

3616
**Release date:** Feb 5, 2026

0 commit comments

Comments
 (0)