Current readiness
This release stores repository requests and generates workflows and Helm values. Automatic worker provisioning and GitHub registration still require a dedicated cloud pool. Creating a request does not start a runner.
Recommended architecture
GitHub Actions Runner Controller (ARC) schedules ephemeral scale-set runners in the dedicated whycloud Cloud cluster. Provider-managed GitHub App credentials live in a secret manager. Runners are not deployed to customer on-premises environments.
Build images with registry cache
The example workflow uses Docker Buildx cache-from/cache-to with registry backends. Your registry must allow authenticated pushes and pulls; keep credentials in GitHub Actions Secrets.
Isolation
DIND-based builds may require privileged containers. Use separate runner nodes, tight egress policy, short-lived credentials and no broad access to the cloud control plane.
Configuration
Open DevOps → Runner, enter owner/repo and generate build.yml and Helm values. Platform operators must provision the cloud worker pool and Github App integration before jobs run.