feat(self-managed): add highAvailability config schema and global.yaml.gotmpl mapping
Open
@shobham-nv is already working on this.
Since Aug 19, 2026.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Description
Add a single highAvailability: block to the self-managed Helmfile stack and wire it through global.yaml.gotmpl onto chart values (replicaCount, affinity, topology spread, PDB, rolling update, Tier-2 sizing).
Profiles: production | staging | single-node.
Nested keys: tier1, nats, openbao, cassandra.
Definition of Done
-
highAvailabilityschema documented/defaulted in env values (environments/base.yamland/or production env) -
global.yaml.gotmplmapshighAvailability.*to existing chart value paths -
helmfile buildwithprofile: productionrenders HA replicas/affinity/PDB -
profile: single-node(orenabled: false) keeps single-replica / soft placement behavior - No requirement for operators to hand-edit per-service manifests
By submitting this issue, you acknowledge that you are an assigned member of the NVCF development team and agree to follow our code of conduct and our contributing guidelines.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.