ARC "no matches for kind AutoscalingRunnerSet" in CI

Helm or kubectl could not find the AutoscalingRunnerSet kind because its CRD is not registered. The gha-runner-scale-set-controller was not installed first, or its version does not match the scale set chart.

What this error means

Installing the scale set fails with "resource mapping not found for kind AutoscalingRunnerSet ... ensure CRDs are installed first" or "no matches for kind".

Error: INSTALLATION FAILED: unable to build kubernetes objects from
release manifest: resource mapping not found for name: "arc-runner-set"
namespace: "arc-runners" from "": no matches for kind "AutoscalingRunnerSet"
in version "actions.github.com/v1alpha1"
ensure CRDs are installed first

Common causes

The controller (and its CRDs) is not installed

The gha-runner-scale-set-controller chart installs the CRDs; without it, the AutoscalingRunnerSet kind is unknown.

Controller and scale set chart version skew

A scale set chart newer than the installed controller may reference a CRD version the controller has not registered.

How to fix it

Install the controller before the scale set

1. Install the gha-runner-scale-set-controller chart, which registers the CRDs.
2. Confirm the CRDs exist with kubectl.
3. Then install the gha-runner-scale-set chart at the same version.

helm install arc \
  oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set-controller \
  --namespace arc-systems --create-namespace
kubectl get crd | grep autoscalingrunnerset

Match controller and scale set chart versions

Install both charts at the same version so their CRD expectations align.

helm list -n arc-systems

How to prevent it

• Install the controller chart first, scale sets second.
• Pin both charts to the same version in every environment.
• Verify the CRDs are present before applying scale sets.

Related guides