sean/zot
Watch
2
0
Fork
You've already forked zot
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
55 commits 2 branches 43 tags 192 KiB
  • Shell 56.7%
  • jq 43.3%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Sean OMeara 2e4319eaaa
 feat(registry): let the builder-images publisher write build/ibmi-analyst 
builder-images added `images/ibmi-analyst` (Ghidra, PowerAS and the rpg-demo
recovery toolkit for the IBM i recovery lane). Its first release built and
exported the image, then `publish-item-ibmi-analyst` died on
`POST /v2/build/ibmi-analyst/blobs/uploads/: DENIED`, exactly the failure the
publisher test documents for a repository without a policy. This adds the
policy beside its siblings, the name to the coupled list, and raises the
counts to 36.

Claude-Session: https://claude.ai/code/session_01HPdKaFBKQVs8hzfgXMrnwV
2026-09-14 17:39:32 +02:00
apps feat: adopt the registry Argo CD application 2026-08-31 23:12:44 +02:00
docs docs: record native availability verification 2026-09-12 17:49:45 +02:00
manifests/registry feat(registry): let the builder-images publisher write build/ibmi-analyst 2026-09-14 17:39:32 +02:00
scripts feat(registry): collect garbage, and keep what cannot be rebuilt 2026-09-09 22:08:37 +02:00
tests feat(registry): let the builder-images publisher write build/ibmi-analyst 2026-09-14 17:39:32 +02:00
BINJOVI.md docs: record native deploy cutover 2026-09-05 21:07:25 +02:00
BINJOVI_NATIVE_DELIVERY.md docs: record native Binjovi delivery 2026-09-05 17:50:43 +02:00
README.md docs: explain native delivery and task telemetry 2026-09-09 18:08:18 +02:00

README.md

sean/zot

The zot OCI registry (registry.sean.farm, namespace registry), decoupled from the retiring sean/pipelines mono-bundle on 2026-08-31.

  • manifests/registry/ — the registry bundle (Namespace, the zot-image-warm hook Job that pulls every zot-v2 image onto zot's node before a rollout, credentials, templated zot config, StatefulSet zot-v2, HTTPRoutes, PDB). Synced by ArgoCD Application/registry.
  • apps/ — the app-of-apps children the zot-argocd root syncs. apps/registry.yaml owns the singleton ArgoCD Application.
  • docs/REGISTRY-AVAILABILITY.md — availability signals, migration gates, the gate ordering rule, and the image warm-up hook.
  • tests/ — the registry's regression guards. Run bash tests/check.sh.

Branch model (fleet standard): feature branches -> trunk (integration) -> main (what ArgoCD tracks). Binjovi owns the release merge and advances main only after it verifies the combined trunk build.

Seeds and backup live elsewhere by design: the ArgoCD AppProject/root App in sean/seanfarm kubernetes/flux/infrastructure/zot-argocd/, the ForgejoRepository + real-time codeberg push mirror in kubernetes/flux/infrastructure/gitmirrors/zot.yaml.

Native pipeline timing

Binjovi uses native agents for this project's Build, Release, and Deploy tasks. The configured deployment target is zot-development. The deployment checks the registry API and verifies a registry write/read probe. Published image identities use immutable digests.

Select an exact successful Build when you release:

binjovictl builds zot
binjovictl release zot --build BUILD_ID --wait
binjovictl status zot

Open the project dashboard and expand an execution attempt to inspect its task timeline and available profiles. The latest completed pipeline summary includes Build and Release time as well as deployment time. Check the Deploy result separately after Release completes. Telemetry explains execution; the stored revision and verification evidence establish completion.