ARC "githubConfigSecret not found" in CI
The scale set points githubConfigSecret at a Kubernetes secret that is missing from the runner namespace. Without it the listener has no credentials and cannot register runners.
What this error means
The controller or listener reports the referenced secret is not found, or the pod stays in CreateContainerConfigError because the secret it mounts does not exist.
controller
Error: secret "pre-defined-secret" not found
(referenced by githubConfigSecret in namespace arc-runners)Common causes
The secret is in the wrong namespace
The secret must live in the same namespace as the scale set; a secret created elsewhere is not found.
The secret name does not match the value
githubConfigSecret names a secret that was never created or is spelled differently.
How to fix it
Create the secret in the runner namespace
- Create the App or PAT secret in the same namespace as the scale set.
- Set githubConfigSecret to that exact secret name.
- Reinstall the scale set and confirm the listener authenticates.
Terminal
kubectl create secret generic pre-defined-secret \
--namespace arc-runners \
--from-literal=github_token=<PAT>Reference the secret by name in values
Point githubConfigSecret at the created secret name so the chart mounts it.
values.yaml
githubConfigSecret: pre-defined-secretHow to prevent it
- Create githubConfigSecret in the scale set namespace before install.
- Keep the secret name and the values reference identical.
- Manage the secret with the same tooling that deploys the scale set.
Related guides
ARC authentication "401 Bad credentials" in CIFix ARC "401 Bad credentials" in CI - the App private key, App ID, installation ID, or PAT in githubConfigSec…
ARC "the GitHub App does not have permission" in CIFix ARC "the GitHub App does not have permission" in CI - the App authenticated but its permission set does n…
ARC "gha-runner-scale-set" Helm install failed in CIFix a failed Helm install of the ARC gha-runner-scale-set chart in CI - bad values, a name clash, or a missin…