Conversation
…nsolidation) Consolidating to single canonical ARC fleet. Killing duplicate lux-build scale set. Build job → hanzo-build-linux-amd64 (max 30 on DO). Deploy job → hanzo-deploy-linux-amd64 (max 20 on DO, correct runner class for kubectl deploys). No behavior change for this workflow.
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
2 participants
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.
Summary
build-lux.yml:lux-build-linux-amd64→hanzo-build-linux-amd64lux-build-linux-amd64→hanzo-deploy-linux-amd64(correct runner class for kubectl work)Why
Duplicate scale sets (lux-build-* and hanzo-build-*) violate "one way to do everything". The hanzo ARC is the canonical fleet per hanzo/CLAUDE.md:
After this and the matching lux/universe PR lands, the lux-build-linux-amd64 scale set spins down to 0 replicas.
Test plan