marco/plugin-barman-cloud
1
0
Fork 0
mirror of https://github.com/cloudnative-pg/plugin-barman-cloud.git synced 2026-01-12 05:33:11 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: describe instanceSidecarConfiguration

Browse Source 
Document how the instance sidecar is configured and what happens when
resources definitions conflict between objectstores.

Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
This commit is contained in:
Francesco Canovai 2025-05-09 12:12:16 +02:00 committed by Marco Nenciarini
parent fd6f3e9b10
commit 86e7377ef9
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
hack/examples/minio-store.yaml
View File

@ -5,7 +5,7 @@ metadata:
spec:
retentionPolicy: "1m"
instanceSidecarConfiguration:
retentionPolicyIntervalSeconds: 30
retentionPolicyIntervalSeconds: 1800
resources:
requests:
memory: "64Mi"
@ -34,4 +34,3 @@ spec:
- "--min-chunk-size=5MB"
- "--read-timeout=60"
- "-vv"

5
web/docs/usage.md
View File

@ -228,7 +228,7 @@ spec:
configuration:
# [...]
instanceSidecarConfiguration:
retentionPolicyIntervalSeconds: 30
retentionPolicyIntervalSeconds: 1800
resources:
requests:
memory: "64Mi"
@ -243,4 +243,5 @@ PostgreSQL instance pod. Even if you define multiple `ObjectStore` resources,
only one sidecar will run per instance. If a replica cluster also archives WALs
to a different `ObjectStore`, the sidecar will use the resource settings from the
`ObjectStore` referenced by the archiving plugin, not the one in the
`.spec.externalClusters` section.
`.spec.externalClusters` section. Changes to the sidecar configuration will be
applied on the next reconciliation of the `Cluster` resources it.