feat: pelican native backups → garage.kian.sh (LB + s3 driver)#258
Merged
Conversation
Adds garage-s3-lb LoadBalancer (MetalLB) with internal external-dns annotations publishing garage.kian.sh, so Wings hosts on VLAN 80 can reach Garage S3 for native in-panel Pelican backups (path-style, endpoint http://garage.kian.sh:3900, bucket pelican-backups). PROMOTE_OVERRIDE=1 (garage is prod-only, no dev pair)
beta35 config/backups.php is env-driven (verify-live #3). Adds APP_BACKUP_DRIVER=s3 + AWS_* endpoint/region/bucket/path-style vars, plus AWS_ACCESS_KEY_ID/SECRET from the pelican-backups-key scoped RW to pelican-backups only (via ExternalSecret -> pelican secret). Var names verified against live beta35 config: path-style flag is AWS_USE_PATH_STYLE_ENDPOINT (not the _BACKUPS_ variant the plan guessed). PROMOTE_OVERRIDE=1 (pelican is prod-only, no dev pair)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase 1 of the pelican-hardening plan. Two commits:
1.
garage-s3-lbLoadBalancer (nsgarage, 1276-prod)Exposes Garage S3 port 3900 on a MetalLB IP with internal external-dns annotations publishing
garage.kian.sh(RFC2136 → Technitium, internal-only). Mirrors thepelican-internalannotation contract. Additive — no change to existinggarage-s3ClusterIP, storage, or configmap.2. Pelican S3 backup driver (ns
pelican, 1276-prod)beta35
config/backups.phpis env-driven (verified against the live container, not assumed). Wires:envs.pelican:APP_BACKUP_DRIVER=s3,AWS_DEFAULT_REGION=garage,AWS_BACKUPS_BUCKET=pelican-backups,AWS_ENDPOINT=http://garage.kian.sh:3900,AWS_USE_PATH_STYLE_ENDPOINT=true.secretEnvs.pelican:AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY← two new keys in thepelicanExternalSecret, backed by BWS. Credentials are a scoped RW key onpelican-backupsonly (GK730fe46da21864df4085b239, owner=false) — the public panel cannot touch thecnpg-pelicanDB-backup bucket.Var-name correction: the plan guessed
AWS_BACKUPS_USE_PATH_STYLE_ENDPOINT; live config readsAWS_USE_PATH_STYLE_ENDPOINT— used the correct name.Safety
PROMOTE_OVERRIDE=1in each commit body (expected per plan README).kustomize buildpasses for both apps; backup env + secretKeyRefs render against thepelicansecret.After merge (owner-gated) → Phase 1 GATE
kubectl -n garage get svc garage-s3-lbIP ==dig +short garage.kian.sh @<internal-dns>.nc -vz garage.kian.sh 3900from a wings host.pelican-backups; restore round-trips.Do not merge without owner approval.
🤖 Generated with Claude Code