Repository navigation
Conversation
…ricsPort, extraPorts schema (ADR-1074) Four gaps where values.yaml / values.schema.json diverged from template usage: 1. nameOverride/fullnameOverride: read by _helpers.tpl but absent from both values.yaml and the root additionalProperties:false schema; any user supplying --set nameOverride=foo received an immediate helm-lint failure. Added as string keys to both files. 2. statefulSet.statePVCSize: statefulset.yaml hardcoded `storage: 1Gi` for the per-replica MCP-state PVC. Exposed as statefulSet.statePVCSize (default 1Gi) and wired into the volumeClaimTemplates storage field. 3. node.metricsPort: port 9090 appeared hardcoded in three template locations (node Deployment containerPort, node-metrics Service port, NetworkPolicy allow rule). Exposed as node.metricsPort (default 9090) and unified. 4. service.extraPorts items schema: bare `"type": "array"` with no items definition accepted malformed port objects silently. Added items schema with required [name, port] and protocol enum. All defaults preserve existing rendered output byte-for-byte. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
lusoris
force-pushed
the
fix/helm-values-completeness-adr-1074
branch
from
June 7, 2026 23:54
f48045a to
816ebcb
Compare
10 tasks done
Contributor
Author
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.
Summary
Four completeness gaps where
values.yaml/values.schema.jsondiverged from template usage, causing either silent misconfiguration or hardhelm lintfailures:nameOverride/fullnameOverrideblocked by schema: both keys are read by_helpers.tplbut absent from theadditionalProperties: falseroot schema, causing immediatehelm lint/helm installfailures for anyone using the standard Helm naming convention. Added as string keys to bothvalues.yamland the schema.1Giliteral instatefulset.yaml:145): exposed asstatefulSet.statePVCSize(default1Gi), wired intovolumeClaimTemplates.9090in 3 locations): node Deployment containerPort, node-metrics Service port, and NetworkPolicy allow rule were all independent literals. Unified undernode.metricsPort(default9090).service.extraPortsitems schema missing: bare"type": "array"with noitemsdefinition silently accepted malformed port objects. Addeditemsschema withrequired: [name, port]andprotocolenum.All four fixes preserve existing rendered output byte-for-byte (defaults match prior hardcoded values).
ADR: ADR-1074
Reproducer / smoke-test
ADR-0108 deliverables checklist
## Alternatives consideredAGENTS.mdinvariant note:deploy/helm/vmafx/AGENTS.md— Invariants (ADR-1074) section addedchangelog.d/fixed/1074-helm-values-completeness.mdfragmentdocs/rebase-notes.mdentry: no rebase impact (Helm-only files)PR hygiene
🤖 Generated with Claude Code