chore: retire the registry bundle from Pipelines #2123

Merged
pipeline-bot merged 1 commit from chore/retire-registry-bundle into trunk 2026-08-31 22:35:49 +00:00
Owner

P2 completes the registry ownership handoff. Pipelines removes Application/registry, bundle/registry, and the registry-only tests and documentation. The existing Prune=false annotation keeps the live Application during the short orphan interval. sean/zot already contains the byte-identical bundle and guards.\n\nThis branch is based on unreleased Pipelines trunk 56f666e9 because it depends on P1. Deletions win for all registry files.\n\nVerification: tests/check.sh passes all 142 guards with zero skips. After this release, sean/zot must add apps/registry.yaml immediately so zot-argocd adopts the live Application.

P2 completes the registry ownership handoff. Pipelines removes Application/registry, bundle/registry, and the registry-only tests and documentation. The existing Prune=false annotation keeps the live Application during the short orphan interval. sean/zot already contains the byte-identical bundle and guards.\n\nThis branch is based on unreleased Pipelines trunk 56f666e9 because it depends on P1. Deletions win for all registry files.\n\nVerification: tests/check.sh passes all 142 guards with zero skips. After this release, sean/zot must add apps/registry.yaml immediately so zot-argocd adopts the live Application.
feat(registry): repoint the registry Application at sean/zot
All checks were successful
pipeline/ci CI green @ e9dd4946c5c8
e9dd4946c5
Migration step P1 of moving the registry out of this retiring repo and
into sean/zot (runbook: sean/zot docs/MIGRATION-RUNBOOK.md).

The one live Application/registry now sources sean/zot manifests/registry
under AppProject zot. The content there is a byte-identical snapshot of
bundle/registry, verified by rendered diff, so this repoint changes no
resource and restarts nothing.

The CR gains the Prune=false pin. That is the handoff mechanism: when step
P2 deletes this block, pipelines-argocd skips pruning the CR instead of
deleting it, the registry keeps running as a live orphan, and zot-argocd
adopts it. The same pinning protects the tetragon seed's CRDs.

registry also leaves the pipelines project's deploy surface: the argocdApps
list and both PipelineTargets. Pipelines deploys neither gate on nor own an
Application that another repo now feeds. gitops-deploy-render-surface pins
the shortened list.

MERGE ORDER — do not merge until all of these hold:
  1. #2119 and #2121 are merged.
  2. seanfarm feat/zot-repo-seed is merged and Flux has applied it.
  3. sean/zot holds the content snapshot and
     hack/refresh-from-pipelines.sh ends "byte-identical: OK" against the
     CURRENT origin/main. If any registry commit landed after the snapshot,
     re-push the snapshot first.

Claude-Session: https://claude.ai/code/session_019JVStQiFwbSLGHArU2sA4X
chore: retire the registry bundle from Pipelines
All checks were successful
pipeline/ci CI green @ 4a3be389544e
4a3be38954
Migration step P2. Step P1 repointed the one live Application/registry at
sean/zot; this commit makes Pipelines forget the registry entirely:

- bundle/registry/ is deleted. sean/zot manifests/registry holds the
  byte-identical successor.
- The Application block is deleted. Its Prune=false pin (added at P1) makes
  pipelines-argocd SKIP pruning the CR: the registry keeps running as a live
  orphan until zot-argocd adopts it, which the runbook does immediately
  after this merge. pipelines-argocd shows OutOfSync only in that window.
- The pipelines AppProject drops the ns registry destination and the
  StatefulSet whitelist entry; nothing left in this repo renders either.
- docs/REGISTRY-AVAILABILITY.md and tests/zot-binjovi-publisher.sh move to
  sean/zot with their input paths re-pointed. The registry-only assertions
  of tests/runtime-bundle-performance.sh move to sean/zot
  tests/zot-runtime-contract.sh; the registry row leaves
  tests/bare-namespace-contract.sh for sean/zot's gateway guard.
- tests/zot-decoupled.sh is the permanent tripwire, mirroring
  tests/ory-binjovi-handoff.sh: re-adopting the registry here is a test
  failure. It is red on the parent commit.

MERGE ORDER: after P1 (feat/zot-repo-repoint) is merged AND verified (app
Synced from sean/zot, zot pod UID unchanged). Then perform the sean/zot
adoption step immediately (sean/zot docs/MIGRATION-RUNBOOK.md step 7).

Claude-Session: https://claude.ai/code/session_019JVStQiFwbSLGHArU2sA4X
sean changed title from chore: retire the registry bundle from Pipelines to WIP: chore: retire the registry bundle from Pipelines 2026-08-31 14:52:03 +00:00
sean changed target branch from main to trunk 2026-08-31 14:54:03 +00:00
sean force-pushed chore/retire-registry-bundle from 4a3be38954
All checks were successful
pipeline/ci CI green @ 4a3be389544e
to 375892fbe9
All checks were successful
pipeline/ci CI green @ 375892fbe97c
2026-08-31 15:46:47 +00:00
Compare
sean force-pushed chore/retire-registry-bundle from 375892fbe9
All checks were successful
pipeline/ci CI green @ 375892fbe97c
to 67573da147
All checks were successful
pipeline/ci CI green @ 67573da1477e
2026-08-31 20:51:29 +00:00
Compare
sean changed title from WIP: chore: retire the registry bundle from Pipelines to chore: retire the registry bundle from Pipelines 2026-08-31 20:51:45 +00:00
sean force-pushed chore/retire-registry-bundle from 67573da147
All checks were successful
pipeline/ci CI green @ 67573da1477e
to 60181b0ca3
All checks were successful
pipeline/ci CI green @ 60181b0ca30f
2026-08-31 22:34:59 +00:00
Compare
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
sean/pipelines!2123
No description provided.