[faust-renovate]

This PR contains the following updates:

Package	Update	Change
dxflrs/garage	minor	v2.4.1 → v2.5.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[faust-renovate]

konflate · #1775 — feat(container): update image dxflrs/garage (v2.4.1 ➔ v2.5.0)

Tip

Routine: only container-image and chart-version changes; 1 resource across 1 app

Blast radius

• Kustomization storage/garage-cluster: 4 dependents (database/cluster, kritika/kritika-db, storage/garage-webui +1 more)

image	from	to	upstream
dxflrs/garage	v2.4.1@sha256:9c96ca…	v2.5.0@sha256:677e5b…	✅

_{konflate 0.6.6 · rendered 53d3655}

[faust-review]

Confidence Score: 5/5

[Critical risk] Upstream explicitly prohibits downgrading once a node runs v2.5.0, so a failed storage rollout cannot be safely recovered by reverting the image and could leave dependent services unavailable.

Not approved: critical risk is above the medium this repository approves

Summary

Bumps Garage from v2.4.1 to v2.5.0 in the GarageCluster CR

The change is one line in kubernetes/apps/storage/garage/cluster/garagecluster.yaml: the GarageCluster's spec.image moves from dxflrs/garage:v2.4.1 to v2.5.0 with a new digest, and konflate renders the cluster diff as that field alone. Merging makes the garage-operator (0.8.2) roll the two storage pods; storage/garage/ks.yaml waits on status.phase Running plus health.healthy, so the Kustomization stays InProgress until the restarted cluster reports healthy, and its four dependents are gated behind that. Two points from the upstream v2.5.0 release notes are worth knowing rather than fixing here: the release is explicitly not backwards-compatible (once a node runs v2.5.0 it must not be downgraded), so reverting this commit after the pods restart is not a safe rollback; and Put/Get/DeleteBucketLifecycle is now restricted to owner-permitted keys, which I searched the repo for (no GarageBucket sets spec.lifecycle, and the operator's bucket and key paths go through the admin API token, not an S3 key), so nothing in-tree exercises it. One open question the notes leave: they recommend adding Garage's new s3_api.public_endpoint to garage.toml, but the operator CRD pinned at 0.8.2 exposes no such field under spec.s3Api (its publicEndpoint is the RPC Service, a different thing), so there is nothing to set here until the operator gains it.

Review context · 4 sources · 6/7 commands

• Sources:
  • https://git.deuxfleurs.fr/api/v1/repos/Deuxfleurs/garage/releases?limit=10
  • https://redirect.github.com/khairul169/garage-webui
  • https://redirect.github.com/rajsinghtech/garage-operator/tree/v0.8.2
  • https://redirect.github.com/rajsinghtech/garage-operator/compare/v0.8.2...main
• Commands run: curl gh jq konflate rg yq

The review's agent was told to submit what it had found on the last step it may take, so it may not cover all it meant to check.

_{Reviews (1) · Last reviewed commit: "feat(container): update image dxflrs/gar..." · self-qwen3.8-flash-next/low}