Port the intended ClickHouse Altinity backup/restore e2e coverage from
cozystack#2600 (never-merged hack/e2e-apps/backup-clickhouse.bats) to the
current Chainsaw approach, reworked on origin/main where the Altinity
backup feature and examples/backups/clickhouse already landed.
Two Tests, etcd-suite shaped:
- clickhouse-backup-1-contracts (CI): a backup-enabled ClickHouse, asserting
the chart<->Altinity-strategy contract against the running cluster — the
clickhouse-backup sidecar on the ch-backup-api :7171 port and the populated
<release>-backup-api-auth Secret the strategy Pod authenticates with. Needs
no reachable object store.
- clickhouse-backup-2-roundtrip: the full Bucket -> BackupJob -> Backup ->
in-place + to-copy RestoreJob round-trip, driving
examples/backups/clickhouse/run-all.sh. Gated out of CI
(CLICKHOUSE_E2E_S3_ROUNDTRIP=1) because kind's self-signed SeaweedFS S3
endpoint cannot be TLS-validated by the in-Pod sidecar.
Wire clickhouse-application -> "clickhouse clickhouse-backup" in
hack/select-e2e.sh so ClickHouse chart edits exercise the backup suite too.
Assisted-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Andrey Kolkov <androndo@gmail.com>
