revert: run upstream zot again until nodes can pull the fork #19
Loading…
Reference in a new issue
No description provided.
Delete branch "revert/zot-seanfarm-fork"
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?
Reverts
d210701(feat(registry): run the seanfarm fork of zot with a bounded S3 retry). Rollback per the plan.The fork image lives on codeberg and the zot pod is pinned to seanfarm-worker-a40389 by its ZFS volume. On that node containerd resolves codeberg.org through registry.sean.farm first; with zot down the mirror answers 503 and the direct codeberg.org fallback also fails (a workflows pod pulling codeberg.org/someara/zdns-builder:v3 is stuck the same way), so the pod stays in ImagePullBackOff and the registry stays down. The upstream image comes from ghcr.io, which is not mirrored, and pulls.
Re-land once the codeberg fallback on that node is proven to work.
https://claude.ai/code/session_01LeVatedQ4sCA1u6LHjo7B5