Document steps for setting up new arm64 self hosted actions runner #16116
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @dims, @chaochn47, @serathius, @ahrtr |
ahrtr
reviewed
Jun 20, 2023
serathius
reviewed
Jun 21, 2023
Signed-off-by: James Blair <mail@jamesblair.net>
ahrtr
approved these changes
Jun 22, 2023
serathius
approved these changes
Jun 22, 2023
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces basic step by step instructions for turning a brand new Equinix Metal
arm64bare metal machine into a github actions runner for etcd project self hostedarm64workflows.Where possible I am relying on existing github documentation.
In future I intend to automate this process further via something like terraform but this basic documentation gives us enough to mark the initial issue as closed and be one step closer to
arm64T1.Fixes #15954