The use of Github App results in "403 Resource not accessible by integration" #3771
Open
7 tasks done
Labels
bug
Something isn't working
community
Community contribution
needs triage
Requires review from the maintainers
Checks
Controller Version
0.27.6
Helm Chart Version
0.23.7
CertManager Version
1.12.1
Deployment Method
Helm
cert-manager installation
I have followed the instructions here:https://github.com/actions/actions-runner-controller/blob/master/docs/installing-arc.md
Cert-manager is working fine.
Checks
Resource Definitions
To Reproduce
Describe the bug
Hi, I am trying to use Github App as the authentication method, but currently this results in an error "403 Resource not accessible by integration". The PAT authentication method works without problems. Here are the details:
--Setup
aks cluster: v1.28.9
actions-runner-controller helm chart version: 0.23.7
controller-image version: 0.27.6
--Description
I am trying to configure actions-runner-controller (with a Helm chart) to run Github actions from a repository (one single repository) in my Github organization (for this Organization I have an owner role). Everything works fine when I configure a PAT token, but when I try to replace the PAT token with a Github App (under the organization, not by using my personal account) I run into the following error: "403 Resource not accessible by integration" . As per my understanding the Github App configuration in Github as well as the values.yaml file for the helm chart installation have been configured correctly:
Github App (which is owned by the organization) has the following permissions:
-Repository Permissions: Actions (read + write), Checks (read + write), Contents (read + write), Metadata (read), Workflows (read + write)
-Organization Permissions: Self-hosted runners (Read + write)
Any help on this issue would be highly appreciated. Thank you.
Describe the expected behavior
I would be able to use the Github App authentication method instead of PAT.
Whole Controller Logs
Whole Runner Pod Logs
The runner pod does not start at all (or then it starts, but terminates immediately).
Additional Context
No response
The text was updated successfully, but these errors were encountered: