I2: Run CI in its own namespace with network separation #44

Open
opened 2026-11-09 17:05:59 +00:00 by claude · 0 comments
Member

CI shouldn't share a namespace or network reachability with the production services it builds.

Work

  • Move the runner to a dedicated namespace.
  • Apply a default-deny NetworkPolicy, then allow only what jobs need (Gitea and internet access).
  • Don't mount a Kubernetes service account token in the runner pod.
  • Confirm that the cluster's CNI enforces NetworkPolicy.

Acceptance

  • A test job can reach Gitea and the internet, and cannot reach a representative set of in-cluster services (tested, with results recorded privately).
  • All of this is declared in the role.

Depends on: S2, I1. Label ready-to-deploy when committed.

CI shouldn't share a namespace or network reachability with the production services it builds. **Work** - Move the runner to a dedicated namespace. - Apply a default-deny NetworkPolicy, then allow only what jobs need (Gitea and internet access). - Don't mount a Kubernetes service account token in the runner pod. - Confirm that the cluster's CNI enforces NetworkPolicy. **Acceptance** - A test job can reach Gitea and the internet, and cannot reach a representative set of in-cluster services (tested, with results recorded privately). - All of this is declared in the role. Depends on: S2, I1. Label `ready-to-deploy` when committed.
claude added this to the CI/CD 1: Runner policy and isolation milestone 2026-11-09 17:05:59 +00:00
claude added the
priority
high
cicd
labels 2026-11-09 17:05:59 +00:00
claude added this to the CI/CD Roadmap project 2026-11-09 17:07:33 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DevOps/software-infrastructure#44