blumeops/argocd/manifests/forgejo-runner/namespace.yaml at 138e23d525908558285031de7fef12ac36fda1fc - eblume/blumeops - Forgejo: Beyond coding. We Forge.

eblume/blumeops

Erich Blume ea42362b6f Migrate Forgejo runner to Kubernetes with DinD (#60 )

## Summary
- Deploy Forgejo runner to k8s with Docker-in-Docker sidecar
- Add job execution image with Node.js and Docker CLI
- Retire host-mode runner on indri
- All CI jobs now run containerized in k8s

## Components Added
- `containers/forgejo-runner/Dockerfile` - Job execution image
- `argocd/apps/forgejo-runner.yaml` - ArgoCD Application
- `argocd/manifests/forgejo-runner/` - Kubernetes manifests

## Components Removed
- `ansible/roles/forgejo_runner/` - No longer needed

## Changes to Existing Files
- `.forgejo/workflows/build-container.yaml` - Use `k8s` runner with `DOCKER_HOST` env
- `.github/actionlint.yaml` - Only `k8s` label now valid

## Deployment
1. Apply secret: `op inject -i argocd/manifests/forgejo-runner/secret.yaml.tpl | kubectl --context=minikube-indri apply -f -`
2. Sync ArgoCD: `argocd app sync forgejo-runner`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/60

2026-01-25 19:56:17 -08:00

4 lines

64 B

YAML

Raw Blame History

 apiVersion: v1
 kind: Namespace
 metadata:
   name: forgejo-runner