# 20230105_fcos-quay-tags Upstream issue: https://github.com/coreos/fedora-coreos-tracker/issues/1367 What can we do with the OSTree repo today? ## Use cases: - pinning on an older version of Fedora CoreOS :37..... :stable-1 :stable-2 - Ensure that when we switch to pulling container images by default, an instance that was powered off for 3 months can still automatically update through the graph This implies that our GC policy cannot be more aggressive than a "reasonable minimum poweroff" timeframe. (We could in theory try to have the client auto-switch to the archive repo but ew) - Debugging problems IMO we should apply a consistent policy with the *application* base image, because that also has all the same bugs. (For example, https://issues.redhat.com/browse/CLOUDBLD-12739) Actually also, we should be consistent with https://pagure.io/releng/issue/11047 ## Proposal: - create versioned tags - prune after 2m (production) 2w (development); extend in future if desired by users - 4 * 3 = 12 tags for prod - 2 * 3 = 6 tags for devel? - at release time, run e.g. `cosa push-container-manifest ... --keep-last N` ? make release job unstable if fails - no fedora-archive repo - no use of quay.io auto-expiration tags due to concerns about pruning when copied to other repos, etc.