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

Update GHAs self-hosted runner docs for arc-v2 #357

Closed
wants to merge 2 commits into from

Conversation

ajschmidt8
Copy link
Member

Changes

This PR updates our GitHub Action self-hosted runner docs in anticipation of our actions-runner-controller v2 rollout.

Background Context

One of the big changes from v1 to v2 is related to how self-hosted runner labels are handled.

v1 allowed us to assign multiple labels to a particular runner set. For example gpu-a100-525-1 and gpu-a100-latest-1 could point to the same set of runners.

For v2, this is not possible. From speaking with the actions-runner-controller devs, this change is intentional. There is an open issue about it here that I am tracking.

As a result of this change, we had to decide whether to strictly use either gpu-a100-525-1-type labels or gpu-a100-{latest,earliest}-1-type labels.

Because of our finite GPU capacity and the overhead associated with manually updating driver-specific labels (e.g. gpu-a100-525-1) across all supported GitHub organizations, we've opted to adopt using the earliest/latest label types.

We will update our runners accordingly if this changes in the future.

@ajschmidt8
Copy link
Member Author

@ajschmidt8
Copy link
Member Author

Closing this PR for now.

See #360 for details.

@ajschmidt8
Copy link
Member Author

superseded by: #367

ajschmidt8 added a commit that referenced this pull request Apr 19, 2023
Duplicate of #357 now that the force push is complete.
@ajschmidt8 ajschmidt8 deleted the ghas-labels branch May 1, 2023 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants