Deploy verification blocked on DinD->in-cluster-registry push reachability (shared, backend#26) #20
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
State
The Forgejo migration (#19) is code-complete and merged on
main:coilysiren-eco-spec-tracker(least-privilege: patch/get deployments, list pods; verified via impersonation).DEPLOY_KUBECONFIGset as a Forgejo Actions secret (serverhttps://192.168.0.194:6443, authenticates as the deployer SA)..forgejo/workflows/build-publish-deploy.ymlin place, mirroring backend's current runner shape (install docker/kubectl static binaries, resolve the DinD host via the job-container gateway, legacydocker build).deploy/main.ymlapp image switched to the registry ref +imagePullPolicy: Always..github/workflows/build-and-publish.ymlremoved.testjob passes (run #15).Blocker (shared, not repo-local)
The
deployjob now gets all the way throughdocker buildand fails only atdocker push:The runner's DinD daemon (reachable at
tcp://172.18.0.1:2375) cannot reach the in-cluster registry NodePort. This is identical tocoilysiren/backend's deploy failure (run #29) and is a property of the shared runner/registry networking, not anything in this repo's workflow. Tracking + fix live in coilysiren/backend#26 (and the registry is coilysiren/infrastructure#168, #171).To finish
Once the DinD-to-registry reachability is fixed upstream, a no-op push to
mainre-runs the pipeline and should deploy green with no further changes in this repo. Verify a pod then pulls192.168.0.194:30500/coilysiren-eco-spec-tracker:<sha>.