You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First I tried installing the chart, then used helm template to debug it.
helm template elastic/eck-beats -f values.yaml
What did you expect to see?
I expected the chart to install successfully.
What did you see instead? Under which circumstances?
Without .Values.spec.type defined
Error: execution error at (eck-beats/templates/beats.yaml:15:11): A Beat type is required
With .Values.spec.type defined
Helm install failed for release elastic-stack/elastic-stack-beats-infra with chart eck-beats@0.9.0: error while running post render on files: map[string]interface {}(nil): yaml: unmarshal errors: line 46: mapping key "type" already defined at line 17
spec:version: {{ required "A Beat version is required" .Values.version }}type: {{ required "A Beat type is required" .Values.spec.type }}{{- if and (not (hasKey .Values.spec "daemonSet")) (not (hasKey .Values.spec "deployment")) }}{{ fail "At least one of daemonSet or deployment is required for a functional Beat" }}{{- end }}{{- toYaml .Values.spec | nindent 2 }}
The template explicitly adds .spec.type from .Values.spec.type and then adds .Values.spec which includes .Values.spec.type again, resulting in a Beats CRD with .spec.type twice.
Environment
ECK version: 2.9, 2.10, 2.11
The text was updated successfully, but these errors were encountered:
Bug Report
What did you do?
First I tried installing the chart, then used
helm template
to debug it.What did you expect to see?
I expected the chart to install successfully.
What did you see instead? Under which circumstances?
Without .Values.spec.type defined
With .Values.spec.type defined
The template explicitly adds
.spec.type
from.Values.spec.type
and then adds.Values.spec
which includes.Values.spec.type
again, resulting in a Beats CRD with.spec.type
twice.Environment
The text was updated successfully, but these errors were encountered: