Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing Actions Runner Controller - Issue #34636

Open
1 task done
seilorjunior opened this issue Sep 18, 2024 · 3 comments · May be fixed by #34637
Open
1 task done

Installing Actions Runner Controller - Issue #34636

seilorjunior opened this issue Sep 18, 2024 · 3 comments · May be fixed by #34637
Labels
actions This issue or pull request should be reviewed by the docs actions team content This issue or pull request belongs to the Docs Content team

Comments

@seilorjunior
Copy link

Code of Conduct

What article on docs.github.com is affected?

https://github.com/github/docs/blob/main/content/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/quickstart-for-actions-runner-controller.md

What part(s) of the article would you like to see updated?

Installing Actions Runner Controller
To install the operator and the custom resource definitions (CRDs) in your cluster, do the following.

In your Helm chart, update the NAMESPACE value to the location you want your operator pods to be created. This namespace must allow access to the Kubernetes API server.
Install the Helm chart.
The following example installs the latest version of the chart. To install a specific version, you can pass the --version argument along with the version of the chart you wish to install. You can find the list of releases in the GitHub Container Registry.

NAMESPACE="arc-systems"
helm install arc
--namespace "{% raw %}${NAMESPACE}{% endraw %}"
--create-namespace
oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set-controller
For additional Helm configuration options, see values.yaml in the ARC documentation.

To enable ARC to authenticate to {% data variables.product.company_short %}, generate a {% data variables.product.pat_v1 %}. For more information, see AUTOTITLE.

Additional information

The first part the process does not work.

If we just run the helm install, we get this error.
helm install arc --namespace arc-systems --create-namespace oci://ghcr.io/actions/actions-runner-controller-charts/gha-runner-scale-set-controller
Error: INSTALLATION FAILED: failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://ghcr.io/token?scope=repository%3Aactions%2Factions-runner-controller-charts%2Fgha-runner-scale-set-controller%3Apull&scope=repository%3Auser%2Fimage%3Apull&service=ghcr.io: 403 Forbidden

@seilorjunior seilorjunior added the content This issue or pull request belongs to the Docs Content team label Sep 18, 2024
Copy link

welcome bot commented Sep 18, 2024

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Sep 18, 2024
@seilorjunior
Copy link
Author

is need to add in the docs that is need to run the gh auth token | helm registry login ghcr.io -u propyless --password-stdin first.

@seilorjunior seilorjunior linked a pull request Sep 18, 2024 that will close this issue
2 tasks
@nguyenalex836
Copy link
Contributor

@seilorjunior Thank you for opening an issue and linking it to your PR! ✨

@nguyenalex836 nguyenalex836 added actions This issue or pull request should be reviewed by the docs actions team and removed triage Do not begin working on this issue until triaged by the team labels Sep 18, 2024
@nguyenalex836 nguyenalex836 linked a pull request Sep 18, 2024 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actions This issue or pull request should be reviewed by the docs actions team content This issue or pull request belongs to the Docs Content team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants