mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-21 12:13:55 +09:00
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 <aleksei.artamonov@aenix.io>
This commit is contained in:
1 parent
dbcc2af679
commit
31b905a1ce
1 file changed
+5
-3
@@ -225,15 +225,17 @@ spec:
|
||||
- name: REMOTE_STORAGE
|
||||
value: s3
|
||||
{{- /*
|
||||
On the useSystemBucket flow every S3 setting, the
|
||||
platform's backupStorage.forcePathStyle included, comes
|
||||
On the useSystemBucket flow every S3 setting but the
|
||||
release's own S3_PATH below, the platform's
|
||||
backupStorage.forcePathStyle included, comes
|
||||
from the clickhouse-backup.yml key the platform projects
|
||||
into cozy-backups-creds, mounted below as the config file.
|
||||
clickhouse-backup reloads that file on every API call and
|
||||
kubelet rewrites a mounted Secret in place, so credentials
|
||||
projected after the Pod started, or rotated since, reach
|
||||
the running sidecar; environment would be read only at
|
||||
start and would override the file, so none is set here.
|
||||
start and would override the file, so none of those is
|
||||
set here.
|
||||
|
||||
S3_FORCE_PATH_STYLE selects path-style vs vhost-style S3
|
||||
addressing. On the legacy paths (own Secret via
|
||||
|
||||
Reference in new issue
Block a user