riotpiao-poimen/homelab
2
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects 1 Releases Wiki Activity

fix: allow CI runner egress to K8s API server #48

Merged
rock merged 1 commits from feat/ci-k8s-api-egress into main 2026-09-13 13:54:32 +00:00
Conversation 0 Commits 1 Files Changed 1
+10
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
k8s/infra/forgejo-runner/templates/networkpolicy.yaml
+10
View File
@@ -29,6 +29,16 @@ spec:
except: except:
- 192.168.1.0/24 - 192.168.1.0/24
- 10.244.0.0/16 - 10.244.0.0/16
# Kubernetes API server — CI needs kubectl access to create
# Tekton PipelineRuns for integration testing.
# The API server runs on control-plane nodes (192.168.1.0/24);
# we allow port 6443 only to that subnet.
- to:
- ipBlock:
cidr: 192.168.1.0/24
ports:
- protocol: TCP
port: 6443
# ingress-nginx, which is how forgejo.riotpiao.com resolves (CoreDNS # ingress-nginx, which is how forgejo.riotpiao.com resolves (CoreDNS
# rewrites that name to ingress-nginx-controller.ingress-nginx.svc). # rewrites that name to ingress-nginx-controller.ingress-nginx.svc).
# Image pushes go to that name so the tag matches what containerd pulls # Image pushes go to that name so the tag matches what containerd pulls