mirror of
https://github.com/cozystack/cozystack.git
synced 2026-10-30 00:27:04 +09:00
Ungate postgres-2-backup-roundtrip: instead of an opt-in env flag it now runs whenever TIA selects the postgres suite (postgres changes, and every release cut), like the other chainsaw tests. The blocker was network placement, not capability: the S3 client is the barman-cloud sidecar inside the Postgres Pod, and the isolated e2e tenant's Cilium egress allowlist blocks it from tenant-root's seaweedfs — so the Test runs in tenant-root (same-tenant egress) against the in-cluster S3 endpoint, trusting its self-signed cert via the copied seaweedfs-system-ca-cert. This is exactly the recipe validated end to end on a real cluster. Also map examples/backups/<app>/ edits to that app's suite in hack/select-e2e.sh (the round-trip executes those scripts as its harness; previously such edits were silently ignored), with bats coverage for both the mapped and the no-suite case. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Signed-off-by: Andrey Kolkov <androndo@gmail.com>
21 lines
859 B
YAML
21 lines
859 B
YAML
# Empty target Postgres instance for the to-copy restore. Keeping the spec
|
|
# minimal - the CNPG driver overlays bootstrap.* and backup.* values when
|
|
# the RestoreJob fires; the chart then renders externalClusters[] from
|
|
# those values so the new cluster's restore_command can fetch WALs from
|
|
# the source's S3 archive.
|
|
#
|
|
# This manifest is the reference for the same-namespace to-copy happy path:
|
|
# deploy it alongside pg-src and the restore leaves the source running. The
|
|
# postgres backup e2e (hack/e2e-chainsaw/postgres, postgres-2-backup-roundtrip)
|
|
# drives exactly this flow via run-all.sh in CI. The
|
|
# cross-tenant variant (target in tenant-test, source's seaweedfs in
|
|
# tenant-root) is blocked by the per-tenant Cilium egress policy.
|
|
---
|
|
apiVersion: apps.cozystack.io/v1alpha1
|
|
kind: Postgres
|
|
metadata:
|
|
name: pg-target
|
|
spec:
|
|
replicas: 2
|
|
size: 5Gi
|