Plan the Linux Forgejo runner migration to Kubernetes #14

New issue

Closed

opened 2026-08-29 00:22:51 -05:00 by portegumi · 1 comment

portegumi commented

2026-08-29 00:22:51 -05:00

Collaborator

Description

Define how the existing Linux Forgejo Actions runner could move into Kubernetes after the cluster is dependable. The Windows runner must remain on its Windows Hyper-V VM to preserve a true Windows execution environment.

Scope

Inventory current Linux runner workloads, labels, privileges, storage, network access, and capacity needs.
Define a Kubernetes runner model, isolation boundary, registration-token handling, caching, and upgrade approach.
Identify bootstrap dependencies so repository delivery does not become circularly dependent on an unhealthy cluster.
Explicitly document the unchanged Windows runner boundary.

Acceptance criteria

Current Linux runner requirements and dependencies are documented.
A proposed Kubernetes runner architecture and security model are documented.
Registration tokens and runner credentials are supplied outside the public repository.
Bootstrap and cluster-outage behavior are addressed.
The Windows Hyper-V runner is explicitly retained for Windows-native execution.
Migration implementation remains deferred until the cluster and Forgejo Actions path are stable.

Dependencies / blockers

Planning can begin after cluster bootstrap; implementation depends on stable networking, storage if required, and a proven Forgejo Actions path.

## Description Define how the existing Linux Forgejo Actions runner could move into Kubernetes after the cluster is dependable. The Windows runner must remain on its Windows Hyper-V VM to preserve a true Windows execution environment. ## Scope - Inventory current Linux runner workloads, labels, privileges, storage, network access, and capacity needs. - Define a Kubernetes runner model, isolation boundary, registration-token handling, caching, and upgrade approach. - Identify bootstrap dependencies so repository delivery does not become circularly dependent on an unhealthy cluster. - Explicitly document the unchanged Windows runner boundary. ## Acceptance criteria - [ ] Current Linux runner requirements and dependencies are documented. - [ ] A proposed Kubernetes runner architecture and security model are documented. - [ ] Registration tokens and runner credentials are supplied outside the public repository. - [ ] Bootstrap and cluster-outage behavior are addressed. - [ ] The Windows Hyper-V runner is explicitly retained for Windows-native execution. - [ ] Migration implementation remains deferred until the cluster and Forgejo Actions path are stable. ## Dependencies / blockers Planning can begin after cluster bootstrap; implementation depends on stable networking, storage if required, and a proven Forgejo Actions path.

portegumi added the

ci-cd

documentation

labels

2026-08-29 00:22:51 -05:00