D4: Create a least-privilege deploy path #72

Open
opened 2026-11-09 17:07:10 +00:00 by claude · 1 comment
Member

Deployments shouldn't run on the shared CI runner. Design a separate deploy runner, reachable only by approved workflows, and a Kubernetes service account limited to the namespaces it deploys. Design how vault material is handled.

Eric: creates and places credentials. No agent reads or handles them.
Claude: writes the role and RBAC, and keeps sensitive details private.

Acceptance: the deploy identity can change its target namespace and is refused elsewhere. A non-approved workflow can't use the deploy runner.

Depends on: I1, I2, I5, D3.

Deployments shouldn't run on the shared CI runner. Design a separate deploy runner, reachable only by approved workflows, and a Kubernetes service account limited to the namespaces it deploys. Design how vault material is handled. **Eric**: creates and places credentials. No agent reads or handles them. **Claude**: writes the role and RBAC, and keeps sensitive details private. **Acceptance**: the deploy identity can change its target namespace and is refused elsewhere. A non-approved workflow can't use the deploy runner. Depends on: I1, I2, I5, D3.
claude added this to the CI/CD 4: Continuous delivery milestone 2026-11-09 17:07:10 +00:00
claude added the cicdneeds-eric
priority
high
labels 2026-11-09 17:07:10 +00:00
claude added this to the CI/CD Roadmap project 2026-11-09 17:07:33 +00:00
Author
Member

Update from D3 (#71), decided 2026-11-10: deploys are human-triggered workflow_dispatch workflows that run the existing Ansible roles. No push-triggered production deploys and no GitOps controller in Phase 0.

For this issue that means:

  • The deploy runner only needs to run Ansible against the cluster for the namespaces of the apps that get a deploy workflow, starting with www (D5, #73).
  • The recommended way to supply credentials is in #71, option 1: Eric provides them to the deploy runner outside Gitea, so the shared runner never holds them. The design note will compare that with repo-scoped Actions secrets before anything is built, and Eric picks.
  • Still blocked on I1 (#43), I2 (#44) and I5 (#47), and keeps needs-eric because Eric creates the credentials.

— eom-cicd-roadmap

**Update from D3 (#71), decided 2026-11-10:** deploys are human-triggered `workflow_dispatch` workflows that run the existing Ansible roles. No push-triggered production deploys and no GitOps controller in Phase 0. For this issue that means: - The deploy runner only needs to run Ansible against the cluster for the namespaces of the apps that get a deploy workflow, starting with www (D5, #73). - The recommended way to supply credentials is in #71, option 1: Eric provides them to the deploy runner outside Gitea, so the shared runner never holds them. The design note will compare that with repo-scoped Actions secrets before anything is built, and Eric picks. - Still blocked on I1 (#43), I2 (#44) and I5 (#47), and keeps `needs-eric` because Eric creates the credentials. — eom-cicd-roadmap
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DevOps/software-infrastructure#72