feat(helm): multi-account support - #79
Open
cxdy wants to merge 1 commit into
Open
Conversation
There was a problem hiding this comment.
Pull request overview
This PR extends the latr Helm chart to support an optional multi-account mode, enabling a single Helm release (and typically one Argo/Flux app) to deploy one latr Deployment per managed Linode account, each with its own ConfigMap/Secret, while sharing a ServiceAccount.
Changes:
- Add
accounts:-driven multi-account rendering (N Deployments, ConfigMaps, Secrets, and per-account PDBs). - Add support for multi-file config via
configFiles(mount under/config, run latr with-config /config/*) in both single-instance and multi-account modes. - Update chart docs/examples and bump chart version to
0.2.0.
Reviewed changes
Copilot reviewed 10 out of 10 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| helm/latr/values.yaml | Documents new accounts structure and optional single-instance configFiles. |
| helm/latr/templates/secret.yaml | Renders one Secret per account in multi-account mode (or none when existingSecret is used). |
| helm/latr/templates/poddisruptionbudget.yaml | Creates per-account PDBs in multi-account mode; keeps single-instance PDB behavior. |
| helm/latr/templates/NOTES.txt | Adds multi-account install notes and adjusts warnings for configFiles. |
| helm/latr/templates/deployment.yaml | Adds multi-account Deployment rendering and configFiles-based -config /config/* support. |
| helm/latr/templates/configmap.yaml | Adds per-account ConfigMaps and supports single/multi-account configFiles and embedded config. |
| helm/latr/templates/_helpers.tpl | Adds multi-account helpers for mode detection, per-account names/labels, and secret name selection. |
| helm/latr/README.md | Documents chart modes and updates example Vault storage path guidance. |
| helm/latr/examples/values-multi-account.yaml | Adds a concrete multi-account values example. |
| helm/latr/Chart.yaml | Bumps chart version from 0.1.0 to 0.2.0. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
cxdy
force-pushed
the
feat/helm-multi-account
branch
from
July 23, 2026 09:58
90dfe0a to
1e8a9aa
Compare
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.
Did some noodling and re-thought my approach in #59 / #58
Adds an optional multi-account mode to the latr Helm chart so a single helm release can run one latr Deployment per managed Linode account. Also bumps the chart version to 0.2.0.
This method gives us many latr pods (one process / account) without +N Applications in Argo/Flux/etc.
Behavior
accounts: []accountsnon-emptyPer account
accounts[].name(e.g.personal-account,work-account)accounts[].idonly ifnameis omitted →latr-<id>(no special public “customer id” concept)configFiles: map of filename → YAML text, mounted at/config-config /config/*(Gofilepath.Glob; no shell)config:as a single latr-native YAML object →config.yamlsecrets.*orsecrets.existingSecretServiceAccountfor the release