fix(promoter): correct Forgejo registry service hostname
CI / CI (pull_request) Failing after 2m6s

forgejo-gitea-http.cicd.svc.cluster.local (headless svc, port 3000)
not forgejo-gitea (doesn't exist). Also wire REGISTRY_BASE env var
in deployment.yaml so it can be overridden without code change.
This commit is contained in:
Admin Bot
2026-09-28 12:34:54 +08:00
parent 23fff1006a
commit 3ca654513f
3 changed files with 21 additions and 9 deletions
+2
View File
@@ -101,6 +101,8 @@ spec:
name: forgejo-registry-pat
key: pat
optional: true
- name: REGISTRY_BASE
value: "http://forgejo-gitea-http.cicd.svc.cluster.local:3000"
volumeMounts:
- name: config
mountPath: /etc/gateway
+9 -4
View File
@@ -158,11 +158,16 @@ spec:
ports:
- protocol: TCP
port: 3000
# Allow to kubernetes API server (ArgoCD Application patching via in-cluster SA)
# Allow to kubernetes API server (ArgoCD Application patching via in-cluster SA).
# kube-apiserver runs on host network (192.168.1.162/166:6443) — must use ipBlock.
# ClusterIP 10.96.0.1:443 also routes there, covered by the 10.96.0.0/12 CIDR.
- to:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: default
- ipBlock:
cidr: 10.96.0.0/12
- ipBlock:
cidr: 192.168.1.0/24
ports:
- protocol: TCP
port: 443
- protocol: TCP
port: 6443