2ad8fc67b8
Create runner deployment with: - ServiceAccount and RBAC for runner pod - ConfigMap for runner configuration - Deployment using code.forgejo.org/forgejo/runner:4.0.1 - Argo CD application for automated deployment Note: Runner requires a sealed secret with registration token. See apps/forgejo-runner/README.md for setup instructions. Part of DEV-334 CI/CD workflow implementation. Co-Authored-By: Paperclip <noreply@paperclip.ing>
69 lines
1.8 KiB
Markdown
69 lines
1.8 KiB
Markdown
# Forgejo Actions Runner
|
|
|
|
This directory contains the deployment configuration for the Forgejo Actions runner.
|
|
|
|
## Prerequisites
|
|
|
|
Before deploying the runner, you need to obtain a registration token from Forgejo.
|
|
|
|
### Getting the Registration Token
|
|
|
|
**Option 1: Via Forgejo Admin UI**
|
|
1. Log in to https://forgejo.basicstack.de as admin
|
|
2. Navigate to Site Administration → Actions → Runners
|
|
3. Click "Create new Runner"
|
|
4. Copy the registration token
|
|
|
|
**Option 2: Via API**
|
|
```bash
|
|
export FORGEJO_TOKEN="your-api-token"
|
|
curl -X POST \
|
|
-H "Authorization: token $FORGEJO_TOKEN" \
|
|
https://forgejo.basicstack.de/api/v1/admin/runners/registration-token
|
|
```
|
|
|
|
### Creating the Secret
|
|
|
|
Once you have the registration token, create a sealed secret:
|
|
|
|
```bash
|
|
# Create a temporary secret file
|
|
kubectl create secret generic forgejo-runner-token \
|
|
--from-literal=token='YOUR_REGISTRATION_TOKEN' \
|
|
--namespace=forgejo \
|
|
--dry-run=client -o yaml > /tmp/runner-token-secret.yaml
|
|
|
|
# Seal it with kubeseal
|
|
kubeseal --format=yaml < /tmp/runner-token-secret.yaml > apps/forgejo-runner/forgejo-runner-token-sealed.yaml
|
|
|
|
# Clean up
|
|
rm /tmp/runner-token-secret.yaml
|
|
```
|
|
|
|
## Deployment
|
|
|
|
The runner is deployed via Argo CD. After creating the sealed secret, apply the Argo CD application:
|
|
|
|
```bash
|
|
kubectl apply -f apps/app-forgejo-runner.yaml
|
|
```
|
|
|
|
## Runner Configuration
|
|
|
|
The runner is configured to:
|
|
- Run 2 concurrent jobs
|
|
- Use Docker-in-Docker for workflow execution
|
|
- Support ubuntu-latest and ubuntu-22.04 labels with Node.js 24
|
|
- Connect to Forgejo at http://forgejo.forgejo.svc.cluster.local:3000
|
|
|
|
## Troubleshooting
|
|
|
|
Check runner logs:
|
|
```bash
|
|
kubectl logs -n forgejo -l app=forgejo-runner -f
|
|
```
|
|
|
|
Check if runner is registered:
|
|
```bash
|
|
kubectl exec -n forgejo deployment/forgejo-runner -- forgejo-runner list
|
|
```
|