At real fleet scale the mirror itself tiers: a central mirror in the cloud fronts
+ upstream once, and every site's mirror pulls from the centre rather than from upstream
+ directly. A new image ripples outward in layers - upstream to the centre, centre to each
+ site as it asks, site to its nodes over the LAN - instead of every site hammering upstream
+ at the same moment. Upstream sees one consumer; each site sees one hop; the nodes never
+ leave the building.
+
Mirrors tier: the load fans out in layers, never all at once.
Build once, promote by copy
Every rebuild is a different artefact - different digest, untested by the stages before it.
So build once, then promote the same digest through environments by copying, registry
@@ -353,7 +360,8 @@
zot
Where the fleet pulls from - a pull-through mirror between the cluster and the
- internet, and the control point for what enters.
+ internet, and the control point for what enters. At fleet scale it tiers: one central
+ mirror in the cloud fans out to per-site mirrors, layering the load.
Leans on it: every image pull on every node - boot, reschedule,
scale-up, recovery.
When it is down: the sharpest edge. Upstream down + mirror up = nobody