Deploy qualified independent Zot blob mounts #77
Loading…
Reference in a new issue
No description provided.
Delete branch "perf/zot-env-mount-rollout"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Pin the serving registry and image warm-up Job to the exact external copy of Zot v3, source991a5a1f, OCI versionv2.1.15-seanfarm.4. Independent mounts use production environment credentials and preserve dedupe=false, existing S3 retry behavior and ordinary-upload fallback.
Validation: all repository guards pass; complete old/new runtime qualification passed on ARM against disposable RustFS, using existing namespaced repositories and a37,748,736-byte blob. Authorized new mount returned201 with no publisher payload; denied sources transferred no content; full digest and source-deletion independence checks passed. Pod/image/node identities and runtime commits were verified. Codeberg and internal indexes match exactly at sha256:a3214366494726c6baef45995a2b41cdaeab9247c51c71a7c45d742c9ab75f52, including both architecture configs.
Production credentials and storage representation stay unchanged. Normal deployment write/read verification remains required. Rollback is the previous .2 image index; no storage migration is needed. No production latency or external signature-copy claim.