GH-5262: fix(helm): chart renders a no-op top-level autopilot block + docs values example drifts from real values.yaml - #5265
Conversation
…values example with real values.yaml (GH-5262) The chart rendered a top-level `autopilot: mode:` key into config.yaml that binds to nothing (autopilot.Config has no `mode` yaml tag) and only triggers the loader's DEPRECATED top-level-autopilot log; the real control is the `--autopilot=<mode>` start arg (hidden alias for --env). Drop the dead block and document why. Also rewrite the docker-helm.mdx values.yaml reference (and every drifted --set example) to match the chart's actual flat schema — no config:/strategy:/existingSecret: keys, ingress.hosts as a list, metrics.serviceMonitor nesting.
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Post-merge review verdict: APPROVE-w-notesBoth spec items correctly implemented; acceptance verified including an actual Notes (filed as a small follow-up): N1 — two install tabs still use the nonexistent |
Summary
Automated PR created by Pilot for task GH-5262.
Closes #5262
Changes
GitHub Issue GH-5262: fix(helm): chart renders a no-op top-level autopilot block + docs values example drifts from real values.yaml
Problem
Two pre-existing chart/docs drifts flagged as out-of-scope in PR#5260 (docs sweep) — filing so the deferral doesn't evaporate (the PR promised follow-ups; none existed).
The Helm chart renders a no-op autopilot config block.
deploy/helm/pilot/templates/configmap.yamlemits a literal top-levelautopilot:with amode:key into the generated config.yaml. The loader deprecation-lifts top-level autopilot blocks now (PR#5253/GH-5255: fix(config): top-level autopilot lift discards all defaults — decode into the default-populated struct, not a zero struct #5256), butmodebinds to NO field on the autopilot config struct (verified: no yaml tag), so the rendered block does nothing except trigger the DEPRECATED log on every tenant start. The chart's actual autopilot control is the--autopilot=<mode>start arg (deploy/helm/pilot/templates/_helpers.tpl~95, a hidden alias for--env). Fix: drop the dead block from the configmap template (the start-arg path is the real one), or render a correctly-nestedorchestrator.autopilotblock if chart users need YAML-level control.The docs values example doesn't match the real values schema.
docs/content/deployment/docker-helm.mdx(~311) shows aconfig:-wrapped values example that does not match the chart's actual flatdeploy/helm/pilot/values.yamlschema. Align the example with the real values file (and if the fix for item 1 changes the rendered shape, do both together).Acceptance
helm templaterender contains no top-level autopilot block that binds to nothing — either the block is gone or it renders correctly nested; no DEPRECATED config log on tenant start from chart-rendered config.helm templateconsumes).Refs