Stand up in-cluster registry foundation #169

Closed
opened 2026-05-28 11:58:59 +00:00 by coilysiren · 0 comments
Owner

Stand up the in-cluster OCI registry and enable the Forgejo runner to push to it. Foundation for the GitHub-free deploy path tracked in #168.

  • registry:2 Deployment/Service/PVC in namespace registry, NodePort 192.168.0.194:30500, pinned to kai-server
  • forgejo-runner DinD --insecure-registry
  • bring-up runbook in k3s-deploy-notes section 11

Host-root registries.yaml + k3s restart is dispatched separately as o2r channel task Q9WR. Per-repo workflow migration + terraform teardown remain under #168.

Stand up the in-cluster OCI registry and enable the Forgejo runner to push to it. Foundation for the GitHub-free deploy path tracked in #168. - registry:2 Deployment/Service/PVC in namespace `registry`, NodePort 192.168.0.194:30500, pinned to kai-server - forgejo-runner DinD `--insecure-registry` - bring-up runbook in k3s-deploy-notes section 11 Host-root registries.yaml + k3s restart is dispatched separately as o2r channel task Q9WR. Per-repo workflow migration + terraform teardown remain under #168.
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
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
coilyco-flight-deck/infrastructure#169
No description provided.