Your own S3 and static sites on a small k3s cluster. Buckets and keys live in one file in Git, and sites go public through Cloudflare Tunnel without opening a single port on your router. Made for people who want object storage and a few static sites at home without port forwarding, an ingress controller, or a list of commands to remember. I can't remember them either, which is why this exists. Why I made it Garage is a great small S3, and it fits in about 30 MiB. But after the first start you have an empty box: the layout, buckets, website access, keys and permissions are all manual, and none of it lives in Git. Rebuild the cluster and you rebuild all of that from memory, and my memory has worse uptime than my cluster. So I wrote it down as code, and this recipe is that code. What you get Garage, Flux-ready. A single-node S3 with website hosting. Setup as code. One spec.json lists your buckets, which ones are websites, and which keys can do what. A Job creates the layout, buckets, keys and credential Secrets, and it's safe to re-run: it only adds, and never deletes. nginx for sites on a volume. For single-page apps and redirects, plus a tool to copy a folder into it. Public with zero open ports. cloudflared connects outbound only, so there's no ingress controller and nothing to forward. Small tools. One uploads a file into a bucket, and one renders a clean index page for public buckets. Optional alerts and a runbook. Four alerts (unhealthy, disk low, resync backlog, errored blocks), and the steps to deploy, verify, route your hostnames and tear down. Made for AI coding agents It 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 (Git pushes, cluster changes, anything at Cloudflare). You approve every change. How it was tested I deployed it on an empty VM and followed the README as written: ✅ Layout, buckets and keys created from an empty Garage ✅ A second run changed nothing (exactly what you want from a setup script) ✅ A file uploaded with a generated key and served at its hostname ✅ nginx served the volume ✅ A test hostname served through a real Cloudflare Tunnel, which the test created and deleted again ✅ Same result on x86_64 and on arm64 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). Those copies are there for when a node goes away; for backups, the backups recipe is the one you want. Public access goes through Cloudflare Tunnel, so that part needs a Cloudflare account (the free plan is enough); the storage itself works without it. What you need k3s v1.35 or newer, with the local-path storage class Flux v2.10 or newer, kubectl, and Python 3 For public access: a domain on Cloudflare and a tunnel token Runs on x86_64 and arm64 (64-bit). Not tested on a Raspberry Pi itself. Pinned versions This recipe: version 1.2.0 k3s v1.37.2 and Flux v2.10.0 Garage v2.5.0 nginx 1.30.6 and cloudflared 2026.10.7