Skip to content

Commit 0809f72

Browse files
Merge branch 'main' into docs/v1.6-kubevirt-migrations
2 parents 7ab90b4 + 2900431 commit 0809f72

3 files changed

Lines changed: 30 additions & 35 deletions

File tree

‎content/en/docs/v1.6/applications/kafka.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -29,13 +29,13 @@ source: https://github.com/cozystack/cozystack/blob/release-1.6/packages/apps/ka
2929

3030
### Application-specific parameters
3131

32-
| Name | Description | Type | Value |
33-
| ---------------------- | --------------------- | ---------- | ----- |
34-
| `topics` | Topics configuration. | `[]object` | `[]` |
35-
| `topics[i].name` | Topic name. | `string` | `""` |
36-
| `topics[i].partitions` | Number of partitions. | `int` | `0` |
37-
| `topics[i].replicas` | Number of replicas. | `int` | `0` |
38-
| `topics[i].config` | Topic configuration. | `object` | `{}` |
32+
| Name | Description | Type | Value |
33+
| ---------------------- | --------------------- | ---------- | ------ |
34+
| `topics` | Topics configuration. | `[]object` | `[]` |
35+
| `topics[i].name` | Topic name. | `string` | `""` |
36+
| `topics[i].partitions` | Number of partitions. | `int` | `0` |
37+
| `topics[i].replicas` | Number of replicas. | `int` | `0` |
38+
| `topics[i].config` | Topic configuration. | `*object` | `null` |
3939

4040

4141
### Kafka configuration

‎content/en/docs/v1.6/applications/mongodb.md‎

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -46,8 +46,9 @@ When `external: true` is enabled:
4646

4747
### Credentials
4848

49-
On first install, the credentials secret will be empty until the Percona operator initializes the cluster.
50-
Run `helm upgrade` after MongoDB is ready to populate the credentials secret with the actual password.
49+
The chart generates the operator's system-user passwords and writes them to `<release>-percona-server-mongodb-users` before the operator starts, so `<release>-credentials` carries a working `password` and `uri` from the first install onwards. An upgrade reuses what the secret already holds and never rotates a live password.
50+
51+
A database created before this behaviour landed keeps the secret the operator generated for it, and its `<release>-credentials` is filled on the next upgrade of the release with the password the operator had already assigned.
5152

5253
### Data lifecycle
5354

@@ -86,13 +87,13 @@ If you need to retain data, take a backup before deletion. Refer to the [Percona
8687

8788
### Upgrading from earlier versions
8889

89-
Earlier versions of this chart referenced a namespace-shared system users secret (`percona-server-mongodb-users`). Upgrading to a release that scopes this secret per CR (`<release>-percona-server-mongodb-users`) triggers a password rotation for the operator-managed system users. The rotation is performed in place by the Percona operator via `db.changeUserPassword()` against the running mongod (operator log: `Secret data changed. Updating users...`); pods are not restarted and the cluster stays available.
90+
Earlier versions of this chart referenced a namespace-shared system users secret (`percona-server-mongodb-users`). A release that scopes this secret per CR (`<release>-percona-server-mongodb-users`) renders the new secret on the next upgrade without rotating anything: while the per-release secret does not exist yet, the chart reads the current system-user passwords back from the operator's own copy, `internal-<release>-users`, and writes those same values into the new users secret and into `<release>-credentials`. The Percona operator sees unchanged values and leaves the running users alone; pods are not restarted and the cluster stays available.
9091

91-
**Rotated automatically on upgrade:**
92+
**Carried over on upgrade:**
9293

93-
- The five operator-managed system accounts: `databaseAdmin`, `userAdmin`, `backup`, `clusterAdmin`, `clusterMonitor`.
94-
- Secret `<release>-percona-server-mongodb-users` (newly created, per-CR) and `internal-<release>-users` receive the new values.
95-
- Secret `<release>-credentials` is regenerated; its `password` and `uri` keys reflect the new `databaseAdmin` password.
94+
- The five operator-managed system accounts: `databaseAdmin`, `userAdmin`, `backup`, `clusterAdmin`, `clusterMonitor` keep their passwords.
95+
- Secret `<release>-percona-server-mongodb-users` is created per CR with the values already held by `internal-<release>-users`.
96+
- Secret `<release>-credentials` is filled with the existing `databaseAdmin` password and the matching `uri`. Installs where these keys were empty get them on the next upgrade, because Helm re-renders only when the spec changes.
9697

9798
**Not affected:**
9899

@@ -101,7 +102,7 @@ Earlier versions of this chart referenced a namespace-shared system users secret
101102

102103
**Action required after upgrade:**
103104

104-
Workloads that mount `<release>-credentials` keep using the cached old password until they re-read the secret. Restart those pods, or run a controller such as [Reloader](https://github.com/stakater/Reloader) to roll them automatically. Without this, application connections fail with authentication errors once their existing sessions expire.
105+
Workloads that mounted `<release>-credentials` while its `password` and `uri` were empty see the filled values only after they re-read the secret. Restart those pods, or run a controller such as [Reloader](https://github.com/stakater/Reloader) to roll them automatically.
105106

106107
**Orphaned legacy secret:**
107108

‎content/en/docs/v1.6/applications/rabbitmq.md‎

Lines changed: 14 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -29,17 +29,17 @@ The service utilizes official RabbitMQ operator. This ensures the reliability an
2929

3030
### Common parameters
3131

32-
| Name | Description | Type | Value |
33-
| ------------------ | ---------------------------------------------------------------------------------------------------------------------------------- | ---------- | --------- |
34-
| `replicas` | Number of RabbitMQ replicas. | `int` | `3` |
35-
| `resources` | Explicit CPU and memory configuration for each RabbitMQ replica. When omitted, the preset defined in `resourcesPreset` is applied. | `object` | `{}` |
36-
| `resources.cpu` | CPU available to each replica. | `quantity` | `""` |
37-
| `resources.memory` | Memory (RAM) available to each replica. | `quantity` | `""` |
38-
| `resourcesPreset` | Default sizing preset used when `resources` is omitted. | `string` | `t1.nano` |
39-
| `size` | Persistent Volume Claim size available for application data. | `quantity` | `10Gi` |
40-
| `storageClass` | StorageClass used to store the data. | `string` | `""` |
41-
| `external` | Enable external access from outside the cluster. | `bool` | `false` |
42-
| `version` | RabbitMQ major.minor version to deploy | `string` | `v4.2` |
32+
| Name | Description | Type | Value |
33+
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------- | ---------- | --------- |
34+
| `replicas` | Number of RabbitMQ replicas. | `int` | `3` |
35+
| `resources` | Explicit CPU and memory configuration for each RabbitMQ replica. Every resource left unset here is taken from `resourcesPreset`. | `object` | `{}` |
36+
| `resources.cpu` | CPU available to each replica. | `quantity` | `""` |
37+
| `resources.memory` | Memory (RAM) available to each replica. | `quantity` | `""` |
38+
| `resourcesPreset` | Default sizing preset. It supplies every resource `resources` does not set, not only a `resources` left empty entirely. | `string` | `s1.nano` |
39+
| `size` | Persistent Volume Claim size available for application data. | `quantity` | `10Gi` |
40+
| `storageClass` | StorageClass used to store the data. | `string` | `""` |
41+
| `external` | Enable external access from outside the cluster. | `bool` | `false` |
42+
| `version` | RabbitMQ major.minor version to deploy | `string` | `v4.2` |
4343

4444

4545
### Application-specific parameters
@@ -70,13 +70,7 @@ resources:
7070
`resourcesPreset` sets named CPU and memory configurations for each replica.
7171
This setting is ignored if the corresponding `resources` value is set.
7272

73-
| Preset name | CPU | memory |
74-
|-------------|--------|---------|
75-
| `nano` | `100m` | `128Mi` |
76-
| `micro` | `250m` | `256Mi` |
77-
| `small` | `500m` | `512Mi` |
78-
| `medium` | `500m` | `1Gi` |
79-
| `large` | `1` | `2Gi` |
80-
| `xlarge` | `2` | `4Gi` |
81-
| `2xlarge` | `4` | `8Gi` |
73+
Presets follow a cloud-style `<series>.<size>` naming convention. Five series cover the full CPU-to-memory ratio range (`t1` 1:0.5, `c1` 1:1, `s1` 1:2, `u1` 1:4, `m1` 1:8) and each series ships eight sizes (`nano` through `4xlarge`). The legacy flat names (`nano`, `micro`, `small`, `medium`, `large`, `xlarge`, `2xlarge`) remain accepted as deprecated aliases of their 1:1 instance-type equivalents.
74+
75+
See [`docs/operations/resource-presets.md`](../../../docs/operations/resource-presets.md) for the full size matrix and the legacy-to-instance-type mapping.
8276

0 commit comments

Comments
 (0)