When installing a Helm chart, an operator needs to override the default container image tag and replica count chosen by the chart author, without editing the chart's templates. Which Helm concept is designed for supplying these customisations at install or upgrade time?
- AChart dependencies, which pull in the required image and replica settings from bundled subcharts.
- BValues, supplied through a values file or command-line overrides, which the chart's templates reference when rendering the final manifests. Correct
- CChart hooks, which execute at defined lifecycle points and set the image tag and replica count for the operator.
- DThe metadata in Chart.yaml, which the operator edits directly to change the image tag and replica count.
Why A is wrong: Tempting because dependencies do influence what a chart installs, but they declare other charts to include, not per-install overrides of image tag or replica count.
Why B is correct: Correct because values are exactly how Helm parameterises a chart, letting an operator override defaults such as image tag and replica count without touching the templates.
Why C is wrong: Tempting because hooks are a real Helm feature, but they run jobs at lifecycle events and are not the mechanism for supplying configuration overrides.
Why D is wrong: Tempting because Chart.yaml is a core chart file, but it holds chart metadata like name and version, not the configurable values consumed by templates.