Issue description:
Two values.yaml inconsistencies in koordinator-yarn-copilot/v0.1.0:
Bug 1 — deployment replicas ignore values
templates/yarn-operator.yaml hardcodes the replica count:
values.yaml has:
koordYarnOperator:
replicas: 2
The template never references it. Setting koordYarnOperator.replicas via --set or values override has no effect.
Fix:
spec:
replicas: {{ .Values.koordYarnOperator.replicas }}
Bug 2 — metrics.addr used in template but absent from values.yaml
templates/yarn-operator.yaml references .Values.koordYarnOperator.metrics.addr:
- --metrics-addr={{ .Values.koordYarnOperator.metrics.addr }}:{{ .Values.koordYarnOperator.metrics.port }}
But values.yaml only defines metrics.port:
koordYarnOperator:
metrics:
port: 8080
metrics.addr is absent — the rendered arg is always --metrics-addr=:8080 and cannot be overridden. The equivalent koord-manager in the koordinator chart explicitly documents addr: "".
Fix: Add to values.yaml:
koordYarnOperator:
metrics:
addr: ""
port: 8080
Issue description:
Two values.yaml inconsistencies in
koordinator-yarn-copilot/v0.1.0:Bug 1 — deployment replicas ignore values
templates/yarn-operator.yamlhardcodes the replica count:values.yamlhas:The template never references it. Setting
koordYarnOperator.replicasvia--setor values override has no effect.Fix:
Bug 2 — metrics.addr used in template but absent from values.yaml
templates/yarn-operator.yamlreferences.Values.koordYarnOperator.metrics.addr:- --metrics-addr={{ .Values.koordYarnOperator.metrics.addr }}:{{ .Values.koordYarnOperator.metrics.port }}But
values.yamlonly definesmetrics.port:metrics.addris absent — the rendered arg is always--metrics-addr=:8080and cannot be overridden. The equivalentkoord-managerin the koordinator chart explicitly documentsaddr: "".Fix: Add to
values.yaml: