Multi Org self-hosted runners

[shashidhar087]

Hello,

We have successfully used the module to host the runners (multiple types) for single Github Org.
Next, we would like to host runners for multi github orgs which may run in multiple AWS accounts.
We are looking for a direction/help/suggestion on the best approach.
Currently, one possible approach is to have one terraform main file per org and per environment.
Assume, we need to host 3 types of runners across 3 Orgs in single AWS account then there would be 9 stacks running.

Features to consider in design:

1. Ephemeral runners
2. Github app webhook based scaling
3. Runner pool per org

We would also like to understand how other companies or teams have set up runners for multi org / multi accounts ?

Thanks for your help !

[ScottGuymer]

If your orgs are all part of the same "enterprise" you can host runners at that level and share them between orgs. I dont think anyone does this yet and it may need some implementation in the module to accommodate. But it might be useful for you.

Failing that i suggest you create an instance of the module per org and runner configuration so yes you would end up with 9.

There has also been some discussion of the module being able to manage multiple runner configs in a single deployment.

[shashidhar087]

I am thinking of github app, webhook and runner infra (lambdas) per github org which would launch N types of runner per org. We have admins per org and they will manage the runner access to repos.

Org A --> Runner A, Runner B, Runner N
Org B--> Runner A, Runner B

Runner A, B ...N is different types of runner like Windows, Linux and customized runners.

In this model, single Infra per org will handle N types of runner instead of runner Infra per runner type which is today.

[ScottGuymer]

I think multi-org is the next logical step once we have the ability to launch different configurations based on labels.

#518

[shashidhar087]

Okay understood. I agree that first we need to support label based launching of runners and then support multi org. Looking forward to this amazing feature. I am open for any discussions/contribution on this.

[mariusfilipowski]

We are also looking forward to these suggested improvements .

We are currently also into checking the options on how to support multiple orgs in GitHub Enterprise Server. We use ephemeral runners with a pool and an idle config. This works great for the org that the module knows about.

What we tried afterwards, is to install the same GitHub App in these different ORGS and give them access. When you start a workflow in another ORG then the current implementation surprisingly starts a new runner (by the message sent webhook) for this org which picks up the jobs after it has registered to this org. What is not possible it to have a pool or idle runners in these other orgs. So this solution suffers from longer start times and possible problems with ephemeral runners. But it works somehow in a multi org scenario.

[mariusfilipowski]

I think multi-org is the next logical step once we have the ability to launch different configurations based on labels.

#518

Hi! Since we now have reached the step to launch different configuration based on labels. What are the next steps (roadmap?) to add multi org support?
Thanks a lot for this great repo, btw.

[mariusfilipowski]

Since this discussion has not progressed for a long time. Is there any chance that this topic has a future or is it already in the "trashcan" ;-)?
Thanks

[npalm]

Supporting multi-org runners is certainly welcome. But for us not urgent since we have using GitHub with a single org. Reason for a single org is to drive an innersource culture.