Deploy self-hosted GitHub Actions runners in the cluster via Actions Runner Controller.
Benefits:
- Faster CI runs (no queue wait for GitHub-hosted runners)
- Access to cluster resources during CI (could enable manifest validation against live cluster)
- Cost savings on GitHub Actions minutes
Considerations:
- Additional resource overhead in the cluster
- Security implications of running CI workloads alongside production
- Only worthwhile if CI workloads justify the overhead
How bjw-s does it: Deploys ARC with labels arc-bjw-s-labs and arc-bjw-s-labs-home-ops, uses self-hosted runners in lint and validation workflows.
Deploy self-hosted GitHub Actions runners in the cluster via Actions Runner Controller.
Benefits:
Considerations:
How bjw-s does it: Deploys ARC with labels
arc-bjw-s-labsandarc-bjw-s-labs-home-ops, uses self-hosted runners in lint and validation workflows.