feat: let the runner build and the cluster pull from the Forgejo registry
- Runner egress: allow 192.168.1.160/32:443. forgejo.riotpiao.com resolves to the ingress LB, inside the 192.168.1.0/24 block the NetworkPolicy denies, so docker push hung until timeout. - dind CA: also mount homelab-ca at /etc/docker/certs.d/forgejo.riotpiao.com/, the path dockerd actually reads for per-registry trust. - Pull secret: dockerconfigjson for the api namespace; /v2/ answers 401. - AppProject: allow the Forgejo repo as a source for api-gw.
This commit is contained in:
@@ -12,6 +12,9 @@ spec:
|
||||
description: Homelab GitOps — single-repo, in-cluster destinations only
|
||||
sourceRepos:
|
||||
- https://github.com/Riotpiaole/riotpiao.homelab.com.git
|
||||
# In-cluster Forgejo — api-gw (k8s/argocd/apps/55-api-gateway.yaml) sources
|
||||
# rock/homelab-frontend from here.
|
||||
- https://forgejo.riotpiao.com/rock/homelab-frontend.git
|
||||
# Public Helm chart repos referenced by k8s/argocd/apps/* and bootstrap/*
|
||||
- https://cloudnative-pg.github.io/charts
|
||||
- https://dl.gitea.com/charts/
|
||||
|
||||
Reference in New Issue
Block a user