Building-permits ops must raise replicaCount for a Helm-packaged cluster component without maintaining a full fork of the upstream chart. Which approach customizes that setting correctly?
Select an answer to reveal the explanation.
Short Explanation
You would not photocopy an entire building-code manual just to change one occupancy number. Helm lets you pass replicaCount (and friends) via values.yaml or --set while keeping the upstream chart. Forking or poking containerd stores is overkill for a values tweak.
Full Explanation
Helm charts expose configuration through values. Operators customize releases with a values file or --set/--set-file flags so parameters such as replicaCount change without maintaining a divergent full chart fork. Direct edits under containerd or kubelet flags are not the Helm customization path.