feat(lago): add api-arm64 subchart for Graviton - #239
Merged
Conversation
INF-379 needs one API replica on arm64 nodes, side by side with the amd64 api, for a pre-flight comparison before the staging-eu pilot. A single Deployment cannot split its replicas across two node architectures, so this adds a second one. api-arm64 is a new lago-rails alias gated by global.arm64.api.enabled (default false). Its values merge api's defaults through a YAML anchor and override only what differs: release name, replicaCount 1, and the nodeSelector and toleration that pin it to the arm64 Karpenter nodepool. The worker gate global.arm64.enabled is renamed to global.arm64.worker.enabled, so the worker and API migrations can phase separately. This is a breaking rename for any consumer of the old flag. The dev-us-1 values move to the new names in lago-deploy. Chart.lock was regenerated via helm dependency update. Chart versions are not bumped here. release.sh bumps every Chart.yaml when the release is cut. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
binaryknot
approved these changes
Aug 28, 2026
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.
What
Adds an
api-arm64subchart tocharts/lagofor the Graviton (arm64)API migration pilot (INF-379). It mirrors the
worker-arm64alias fromINF-375.
lago-railsaliasapi-arm64, gated byglobal.arm64.api.enabled(default false).
api's shape via a YAML anchor. Overrides onlynameOverride: lago-api-arm64,replicaCount: 1, and the arm64nodeSelector+ toleration.Breaking change
The worker gate
global.arm64.enabledis renamed toglobal.arm64.worker.enabled. The worker and API migrations now phaseindependently. Any consumer of the old flag must move to the new name.
The only current consumer is dev-us-1, updated in the paired lago-deploy
PR.
Verification
helm unittest charts/lago— 57 tests pass (newapi_arm64_test.yaml;worker_arm64_test.yamlupdated to the new gate name).helm template: both gates off by default render zero arm64 resources.The old
global.arm64.enabledflag no longer triggers worker-arm64.Notes
Chart versions are not bumped here.
release.shbumps them when therelease is cut (→
0.12.0). The lago-deploy pin waits for that release.🤖 Generated with Claude Code