Update GHAs self-hosted runner docs for arc-v2
#357
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
tov2
is related to how self-hosted runner labels are handled.v1
allowed us to assign multiple labels to a particular runner set. For examplegpu-a100-525-1
andgpu-a100-latest-1
could point to the same set of runners.For
v2
, this is not possible. From speaking with theactions-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 orgpu-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 theearliest
/latest
label types.We will update our runners accordingly if this changes in the future.