{"meta":{"title":"Support for Actions Runner Controller","intro":"What to know before you contact GitHub Support for assistance with Actions Runner Controller.","product":"GitHub Actions","breadcrumbs":[{"href":"/en/actions","title":"GitHub Actions"},{"href":"/en/actions/concepts","title":"Concepts"},{"href":"/en/actions/concepts/runners","title":"Runners"},{"href":"/en/actions/concepts/runners/support-for-arc","title":"Support for ARC"}],"documentType":"article"},"body":"# Support for Actions Runner Controller\n\nWhat to know before you contact GitHub Support for assistance with Actions Runner Controller.\n\n## Overview\n\nThe Actions Runner Controller (ARC) project [was adopted by GitHub](https://github.com/actions/actions-runner-controller/discussions/2072) to release as a new GitHub product. As a result, there are currently two ARC releases: the legacy community-maintained ARC and GitHub's Autoscaling Runner Sets. GitHub's Autoscaling Runner Sets work with both Kubernetes and OpenShift.\n\nGitHub only supports the latest Autoscaling Runner Sets version of ARC. Support for the legacy ARC is provided by the community in the [Actions Runner Controller](https://github.com/actions/actions-runner-controller) repository only.\n\n## Scope of support for Actions Runner Controller\n\nTo ensure a smooth adoption of Actions Runner Controller, we recommend that organizations have staff with expert-level knowledge of container orchestration. Many aspects of ARC installation, including orchestration, networking, policy application, and integration with managed cluster providers, fall outside GitHub Support's scope and require in-depth knowledge of your clustering tools (i.e. Kubernetes or OpenShift). If your support request is outside of the scope of what our team can help you with, we may be able to recommend next steps to help resolve your issue or provide other guidance. Your support request is out of GitHub Support's scope if the request is primarily about:\n\n* The legacy community-maintained version of ARC\n* Installing, configuring, or maintaining dependencies\n* Template spec customization\n* Container orchestration, such as Kubernetes/OpenShift setup, networking, building images in ARC (DinD), etc.\n* Applying cluster policies\n* Managed container orchestration providers or provider-specific configurations\n* [Runner Container Hooks](https://github.com/actions/runner-container-hooks) in conjunction with ARC's `kubernetes` mode\n* Installation tooling other than Helm\n* Storage provisioners and PersistentVolumeClaims (PVCs)\n* Best practices, such as configuring metrics servers, image caching, etc.\n\nWhile ARC may be deployed successfully with different tooling and configurations, your support request is possibly out of GitHub Support's scope if ARC has been deployed with:\n\n* Installation tooling other than Helm\n* Service account and/or template spec customization\n\nFor more information about contacting GitHub Support, see [Contacting GitHub Support](/en/support/contacting-github-support).\n\n> \\[!NOTE]\n>\n> * ARC is only supported on GitHub Enterprise Server versions 3.9 and greater.\n\n## Working with GitHub Support for Actions Runner Controller\n\nGitHub Support may ask questions about your Actions Runner Controller deployment and request that you collect and attach [controller logs, listener logs](/en/actions/tutorials/use-actions-runner-controller/troubleshoot#checking-the-logs-of-the-controller-and-runner-set-listener), runner logs, and Helm charts (`values.yaml`) to the support ticket."}