feat(docker-release-split): default the legs to the EKS/ARC runner scale sets - #57
Merged
Merged
Conversation
…ale sets The org's self-hosted runners are live: pinpredict-dev (amd64) and pinpredict-dev-arm64 (arm64). Make them the split legs' defaults so every caller gets native in-VPC builds without passing runner inputs — with ARC the scale set name is the runs-on label (scale sets take no extra labels), and same-VPC ECR keeps image pushes and registry-cache traffic local. amd64-runner/arm64-runner still override, e.g. back to GitHub-hosted ubuntu-24.04 / ubuntu-24.04-arm.
This file contains hidden or 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
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.
The EKS/ARC runners are live, with one scale set per architecture:
pinpredict-dev(amd64) andpinpredict-dev-arm64(arm64). This flipsdocker-release-split.yml's leg defaults to them, so every caller gets native, in-VPC builds with zero config — k5s (merged in k5s#96 with no runner inputs) picks these up on its next run automatically.Notes:
runs-onlabel — scale sets take no additional labels, so this is the whole wiring.cache: registrytraffic stay local instead of crossing the internet from hosted runners.amd64-runner/arm64-runnerstill override per caller — e.g. GitHub-hostedubuntu-24.04/ubuntu-24.04-arm(arm64 standard runners work in private repos since Jan 2026).actions-runner-controller.yaml) were sized for light CI — build legs will want more; and dind is already enabled, which the stevedore action's buildx setup uses as-is.Sequencing with the k5s bring-up: platform-gitops#1295 (the missing
xp-k5s-gha-pushrole) is the actual blocker for k5s's first release; this PR can merge before or after — the re-run will use whatever defaults are on@mainat that moment.