docs(backups): drop the claim that a region change needs a ClickHouse restart

The ClickHouse sidecar on the system bucket no longer reads S3 settings
from environment set at start, so a re-projected region reaches it
without a Pod rollout, and the contracts fixture no longer depends on
optional Secret keys to start its Pod.

Assisted-by: LLM
Signed-off-by: Alexey Artamonov <aleksei.artamonov@aenix.io>
This commit is contained in:
Alexey Artamonov committed 2026-11-04 19:31:59 +03:00
1 parent e752952047
commit 2e37aaec5f
2 files changed
+2 -6

No files matched your search

@@ -8,8 +8,8 @@
# backup.enabled=true with placeholder S3 coordinates is deliberate: the
# sidecar runs `clickhouse-backup server`, which starts its HTTP API without
# validating S3 (ALLOW_EMPTY_BACKUPS=true, lazy connect — the same reason the
# platform useSystemBucket flow marks the S3 secret keys optional so the Pod
# starts before any bucket is projected). So the Pod becomes Ready and the
# platform useSystemBucket flow can start the Pod before any bucket is
# projected). So the Pod becomes Ready and the
# chart<->strategy contract is assertable with no reachable object store. The
# real S3 backup/restore round-trip lives in clickhouse-2-backup-roundtrip,
# which runs in tenant-root against the in-cluster SeaweedFS.
@@ -105,10 +105,6 @@ backupStorage:
endpoint: http://seaweedfs-s3.tenant-root.svc.cozy.local:8333
# region is re-projected into cozy-backups-creds on the next reconcile
# (1-minute tick for system namespaces, on-demand for tenant namespaces).
# However, charts that consume the region via secretKeyRef in env vars —
# the chart-emitted ClickHouse sidecar on `useSystemBucket: true` is the
# only such consumer today — only pick up the new value on Pod restart.
# Plan a rollout of those Pods when you change this value.
region: us-east-1
forcePathStyle: true
# systemSecretName — the human-friendly Secret produced by the Bucket