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

CI runner needs kubectl access to create Tekton PipelineRuns for integration testing. ## Root Cause The runner egress NetworkPolicy blocks `192.168.1.0/24` (LAN). The K8s API server runs on control-plane nodes in that subnet (`192.168.1.166:6443`). kubectl from inside the DinD container times out. ## Fix Allow TCP port 6443 to `192.168.1.0/24` — scoped to control-plane API server only. ## Required By homelab-frontend PR #25 (Tekton integration testing) — CI creates PipelineRuns via kubectl. --------- Co-authored-by: rock <[email protected]> Reviewed-on: #48 Co-authored-by: poimen <[email protected]>
2026-09-13 13:54:31 +00:00
parent 7a5d0a83d5
commit 4b5ecfcd49
1 changed files with 10 additions and 0 deletions
@@ -29,6 +29,16 @@ spec:
            except:
              - 192.168.1.0/24
              - 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
    # rewrites that name to ingress-nginx-controller.ingress-nginx.svc).
    # Image pushes go to that name so the tag matches what containerd pulls