actions / actions/actions-runner-controller

Support self-hosted organisation runners without granting complete admin permissions

Open
#2,249 2 comments 14 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement needs triage
Dominant language
Go
Stars
6.5k
Forks
1.5k
Avg merge
2d 2h
Merged PRs (30d)
27

Description

What would you like added?

I would like to have the ability to run runners for a whole organization without granting a token with organization admin rights to the controller.

A clear and concise description of what you want to happen.

Note: Feature requests to integrate vendor specific cloud tools (e.g. awscli, gcloud-sdk, azure-cli) will likely be rejected as the Runner image aims to be vendor agnostic.

Why is this needed?

It would allow minimizing potential consequences of token leakage and reduce security risks.
A clear and concise description of any alternative solutions or features you've considered.

Additional context

As far as I understood, it seems that right now it's not yet supported in runner itself - https://github.com/actions/runner/issues/443#issuecomment-663168938

Unfortunately, I haven't found a disccussion/issue for adding support to run organisation level runners without granting an admin token.

Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked GitHub Actions Runner issue #443 and the controller's existing organization-runner authentication flow. Determine whether upstream supports this permission model; done means organization-level self-hosted runners work without giving the controller organization-admin credentials, with the security behavior documented and tested.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, kubernetes
Domain
devops, infrastructure, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.