Skip to content

Commit 7540082

Browse files
committed
chore: bump up clickhouse-backup
1 parent 04024c0 commit 7540082

3 files changed

Lines changed: 3 additions & 3 deletions

File tree

addons/clickhouse/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1409,7 +1409,7 @@ The incremental backup's `parentBackupName` must refer to an existing backup cre
14091409
> [!NOTE]
14101410
> When the restore target has TLS enabled, the restore job mounts the ClickHouse TLS files and connects through the secure TCP port.
14111411
1412-
Restore process will restore schema first, then restore data. Non-TLS restores also restore RBAC metadata; TLS restores focus on schema and data because replicated RBAC backup requires a direct Keeper TLS connection. You can tune schema-ready waiting behavior for restore jobs via Helm values:
1412+
Restore process will restore schema and RBAC metadata first, then restore data. When the restore target has TLS enabled, the restore job uses the secure ClickHouse TCP port and Keeper TLS settings for RBAC metadata. You can tune schema-ready waiting behavior for restore jobs via Helm values:
14131413
14141414
```yaml
14151415
restore:

addons/clickhouse/values.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ backupImage:
5757
registry: ""
5858
repository: apecloud/clickhouse-backup-full
5959
pullPolicy: IfNotPresent
60-
tag: 2.6.42
60+
tag: 2.7.0
6161

6262
restore:
6363
schemaReadyTimeoutSeconds: 1800

examples/clickhouse/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -629,7 +629,7 @@ The incremental backup's `parentBackupName` must refer to an existing backup cre
629629
> [!NOTE]
630630
> When the restore target has TLS enabled, the restore job mounts the ClickHouse TLS files and connects through the secure TCP port.
631631
632-
Restore process will restore schema first, then restore data. Non-TLS restores also restore RBAC metadata; TLS restores focus on schema and data because replicated RBAC backup requires a direct Keeper TLS connection. You can tune schema-ready waiting behavior for restore jobs via Helm values:
632+
Restore process will restore schema and RBAC metadata first, then restore data. When the restore target has TLS enabled, the restore job uses the secure ClickHouse TCP port and Keeper TLS settings for RBAC metadata. You can tune schema-ready waiting behavior for restore jobs via Helm values:
633633
634634
```yaml
635635
restore:

0 commit comments

Comments
 (0)