Allow removal of default runner tags

[sbrinkerhoff]

Describe the enhancement

Allow a flag (or another mechanism) to remove the default self-hosted, ${operating_system} and ${operating_system_arch} labels when connecting to a privately hosted Github Enterprise installation.

Code Snippet
n/a

Additional information

The current Github Runner agent adds default labels that include the self-hosted, operating system and architecture.

For enterprise rollouts we have a desire for Runners to be attached as an organizational default pool, org specific pools and repo specific pools we have noticed that folks following the default installation instructions will generally not initially tag their runners. The default workflows then use something such as self-hosted as the target. This generally works as long as their runner is the only runner attached.

Occasionally a group will attach another set of runners at an org level and it contains the same default tag. Without any clear change at the repo level, now the runner is randomly scheduled as the repo runner or the org runner.

Additionally some orgs may wish to manage an inhouse set of runners that are available to all orgs. In this case, they can inadvertently be used as well.

While internal documentation and best practice can help in this scenario, having a mechanism that allows the default tags to be removed and replaced would allow our enterprise-wide runners to not attach with self-hosted, and instead attach as enterprise-self-hosted or similar.

This would reduce the chances of a team accidentally building on a runner they did not intend to build on.

[TingluoHuang]

@thejoebourneidentity for this product question.

[andrew-sledge]

Upvoting - in a sufficiently large organization the current state will become a management nightmare.

[ethomson]

We've removed the defaults for operating system and operating system architecture. I think that there's an opportunity to tackle self-hosted as well, but we don't have this work planned at the moment.

Is self-hosted also a management nightmare for you @sbrinkerhoff and @andrew-sledge, or have these changes helped a bit?

Thanks much for the feedback.

[sbrinkerhoff]

Thanks so much. We’re on self-hosted GHES so these updates take a while for us to be able to use generally. The self-hosted has been mostly mitigated with training, at first we were running into significant usage of it which would cause folks to swap between builder pools. We’re also working to subset team-specific builders which makes the issue even less critical than it was early on.

…

On Fri, Dec 17, 2021 at 3:35 PM Edward Thomson ***@***.***> wrote: We've removed the defaults for operating system and operating system architecture. I think that there's an opportunity to tackle self-hosted as well, but we don't have this work planned at the moment. Is self-hosted *also* a management nightmare for you @sbrinkerhoff <https://github.com/sbrinkerhoff> and @andrew-sledge <https://github.com/andrew-sledge>, or have these changes helped a bit? Thanks much for the feedback. — Reply to this email directly, view it on GitHub <#1240 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACO72MXWVJNUA5H6TCNJ7LURONHRANCNFSM5BPRYQTQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>