Added a second dedicated Gitea Actions runner to increase CI capacity without sharing the existing runner identity.
- Created host data directory:
/mnt/fastdata/k8s-pvcs/gitea/act-runner-2
- Applied Kubernetes Deployment:
gitea/gitea-act-runner-2
- Registered runner name:
drg-k8s-runner-2
- Reused existing runner config and registry CA ConfigMaps:
gitea-act-runner-configgitea-registry-ca
- Reused existing runner environment Secret:
gitea-act-runner-env
- Deployment
gitea-act-runner-2 rolled out successfully.
- Pod was Ready with both containers running:
dind and runner.
- Registration log reported
Runner registered successfully.
- Runner daemon declared successfully with labels:
ubuntu-latestubuntu-24.04ubuntu-22.04
- Runner received an Actions task after startup, confirming scheduling from Gitea.
- The existing runner was not scaled because it uses a shared
/data/.runner identity path.
- This runner uses a separate
/data path to avoid duplicate runner identity issues.
- DinD remains privileged, matching the existing runner architecture.
- Stale failed pods from older runner ReplicaSets were observed but not cleaned up as part of this change.