feat(lago): add worker-arm64 subchart for the Graviton pilot - #237
Merged
Conversation
INF-375 needs a Sidekiq worker running on arm64 nodes, side by side with the existing amd64 worker, for an hours-scale comparison before scaling up. A single Deployment can't split its replicas across two node architectures, so this adds a second one. worker-arm64 is a new lago-rails alias gated by global.arm64.enabled (default false), so bumping this chart's version is a no-op on any cluster without an arm64 nodepool. Its values merge worker's defaults through a YAML anchor and override only what differs: release name, replicaCount: 1, and the nodeSelector/toleration that pin it to the arm64 Karpenter nodepool added in lago-infrastructure PR #1595. Chart.lock was regenerated via `helm dependency update`. Chart versions are not bumped here — release.sh's workflow_dispatch step bumps every Chart.yaml automatically when the release is cut.
binaryknot
approved these changes
Aug 26, 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.
Summary
worker-arm64subchart (alias oflago-rails) for INF-375 — the dev-us-1 pilot of the Graviton worker migration. Gated byglobal.arm64.enabled(defaultfalse), so this is a no-op for every cluster until a values file opts in.worker-arm64mergesworker's existing values through a YAML anchor (&workerDefaults/<<: *workerDefaults) instead of duplicating the block, since the two are identical except for release name, replica count, and scheduling. This differs from the other named workers in this chart (billing-worker,wallets-worker, etc.), which each have a genuinely different container command.nodeSelector/tolerationsmatch the arm64 Karpenter nodepool taint and label added inlago-infrastructurePR #1595 (arch: arm64,NoSchedule).Chart.lockregenerated viahelm dependency update. Chart versions are intentionally not bumped —release.sh'sbump_versionsstep does that automatically when the release is dispatched.Known limitation
helm-docsdoesn't render the YAML-anchor merge correctly — it emitsworker-arm64.<<.*rows carryingworker's stale defaults. I leftREADME.mdunregenerated rather than commit misleading docs; happy to hand-write a cleanworker-arm64doc block if that's wanted before merge.Test plan
helm unittest charts/lago— 7 suites / 54 tests pass, including the newtests/worker_arm64_test.yaml.helm templatewithglobal.arm64.enabled=true—worker-arm64renders with the same command/env asworker, plusreplicas: 1,nodeSelector: {arch: arm64}, and the matching toleration.helm templatewith the flag unset (default) — zeroworker-arm64resources render.workflow_dispatchrelease: wireglobal.arm64.enabled: trueand aworker-arm64override intolago-deploy's dev-us-1mainpreview values, confirm the pod schedules onto an arm64 node and reachesReady.