Skip to content

README.md

Latest commit

 

History

History
61 lines (42 loc) · 1.55 KB

README.md

File metadata and controls

61 lines (42 loc) · 1.55 KB
Raw

github-scaling-explicit

What This Demonstrates

GitHub-first explicit scaling on ImpVMRunnerPool using spec.scaling mode controls.

Why It Matters

  • no implicit capacity defaults for GitHub scaling pools
  • explicit hard ceilings and pace controls
  • clear mode selection (webhook, polling, hybrid) in spec.scaling.mode

Manifests

  • impnetwork.yaml: isolated network for runner VMs
  • impvmclass.yaml: compute profile
  • impvmtemplate.yaml: runner VM template
  • impvmrunnerpool.yaml: explicit scaling configuration

Important

Set these scaling fields explicitly:

  • mode
  • minIdle
  • maxConcurrent
  • scaleUpStep
  • cooldownSeconds

GitHub (platform.type=github-actions) is supported for this explicit scaling mode in this first version.

Prerequisites

  • Secret default/github-imp-runners exists with the GitHub App fields github-app-id, github-app-installation-id, and github-app-private-key
  • Secret default/gh-webhook-secret exists
  • set platform.scope.org to your organization; a named GitHub runner group requires organization scope

Do not put a JIT registration value in the manifest or the base image. Imp mints one registration configuration per runner VM and passes it to the guest only at launch time.

Apply

kubectl apply -f examples/github-scaling-explicit/

Verify

kubectl get impvmrunnerpool ci-runner-explicit -n default -o yaml
kubectl get impvms -n default -l imp.dev/runner-pool=ci-runner-explicit

Cleanup

kubectl delete -f examples/github-scaling-explicit/