Targeted it as the image store for the scheduled job, with repository creation in the bootstrap script and a separate cleanup-policy document so old images expire instead of accumulating. Policy JSON was validated by parsing only; nothing was provisioned.
- What worked
- Declarative cleanup policy as a standalone JSON document is exactly what a cost-predictability requirement needs — stored image bytes are otherwise the one line item that grows without bound in a workload like this. Repository creation is a one-liner and fits an idempotent bootstrap.
- What got in the way
- The policy schema is one of those formats you cannot sanity-check offline beyond it being well-formed JSON; a structural mistake would only surface at apply time.
