Garage, Flux-ready
A single-node S3 with website hosting, running from your Git repository.
rttf · recipe pack · version 1.2.0
Garage S3 and nginx on your k3s cluster, with every bucket and key described in one file in Git. Sites go public through Cloudflare Tunnel, so nothing is forwarded on your router.
The problem
Layout, buckets, website access, keys and permissions: all manual, none of it in Git. Rebuild the cluster and you rebuild your storage from memory, which is the worst place to keep a config. And to make a site public you forward a port or run an ingress controller.
spec.json
What you get
Flux manifests, a setup Job, a few small tools and a runbook. Describe your buckets, push, and the cluster does the rest.
A single-node S3 with website hosting, running from your Git repository.
One spec.json: buckets, which are websites, which keys can do what. A Job creates them and the credential Secrets.
The Job only adds. It never deletes a bucket or revokes a key; a second run changes nothing.
cloudflared connects outbound only. No ingress controller, nothing to forward.
Single-page apps and redirects from a volume, plus a tool to copy a folder into it.
Upload a file into a bucket, render an index page for public buckets, and four optional alerts.
Made for AI coding agents
The recipe ships with an AGENTS.md and a CLAUDE.md written as an operating procedure: what to ask you, what to check first, the exact steps, how to verify, and where to stop for your approval.
# following recipes/garage-static-web/AGENTS.md
? Which buckets, which are websites, and which hostnames?
✓ preflight: nodes Ready, Flux healthy, local-path present
✓ spec.json written, bootstrap manifest rendered
? Ready to commit and push to your Flux repo. Proceed? [y/N]
? Add the hostname routes at Cloudflare? [y/N]
✓ buckets and keys created, page served at its hostname
Illustration of the steps in AGENTS.md, not a recorded session.
Tested, not promised
On x86_64 and again on arm64. Every check below passed, and each run started from VM creation.
Is it for you?
Yes, if you want buckets and static sites on your own k3s cluster, described in Git and reachable from the internet without port forwarding.
No, if you want more than three nodes or several sites set up for you. Garage can do both (more nodes, zones per site), but this recipe is built and tested for one node, or three with a copy on each (new in 1.2).
local-path storage classkubectl, Python 3Questions
Only for public access. Garage, the buckets, keys and nginx all work without it, and most of the README's checks need no Cloudflare. For public sites you need a domain on Cloudflare; the free plan is enough.
Yes. Edit spec.json, render the manifest again, and push. The Job adds what is new.
No. The setup Job only adds: it never deletes a bucket or revokes a key. The test ran it twice; the second run changed nothing.
With three nodes, yes: the optional three-node setup keeps three copies, one per node, and any one node can go without S3 going down (new in 1.2, measured in the README). The default is one node with one copy. Either way, copies are not backups: pair it with the backups recipe, which mirrors your buckets every night and tests the restore every week.
It runs on 64-bit ARM: it was tested from zero on an arm64 VM. It was not tested on a Pi itself, and 32-bit ARM is not supported.
Describe your buckets once, keep them in Git, publish sites without opening a port. Tested from zero on x86_64 and arm64.
Get the recipe €19