Skip to content

Commit bfac571

Browse files
committed
docs(clickhouse): note that the backup path stays in the sidecar environment
The chart comment said every S3 setting of the system-bucket flow comes from the mounted config file, but S3_PATH is still set in the environment: the platform's file carries no path, and the prefix belongs to the release rather than to the platform. Assisted-by: LLM Signed-off-by: Alexey Artamonov <[email protected]>
1 parent cb49312 commit bfac571

1 file changed

Lines changed: 5 additions & 3 deletions

File tree

‎packages/apps/clickhouse/templates/clickhouse.yaml‎

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -225,15 +225,17 @@ spec:
225225
- name: REMOTE_STORAGE
226226
value: s3
227227
{{- /*
228-
On the useSystemBucket flow every S3 setting, the
229-
platform's backupStorage.forcePathStyle included, comes
228+
On the useSystemBucket flow every S3 setting but the
229+
release's own S3_PATH below, the platform's
230+
backupStorage.forcePathStyle included, comes
230231
from the clickhouse-backup.yml key the platform projects
231232
into cozy-backups-creds, mounted below as the config file.
232233
clickhouse-backup reloads that file on every API call and
233234
kubelet rewrites a mounted Secret in place, so credentials
234235
projected after the Pod started, or rotated since, reach
235236
the running sidecar; environment would be read only at
236-
start and would override the file, so none is set here.
237+
start and would override the file, so none of those is
238+
set here.
237239

238240
S3_FORCE_PATH_STYLE selects path-style vs vhost-style S3
239241
addressing. On the legacy paths (own Secret via

0 commit comments

Comments
 (0)