Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Allow array values for extra #1451

Closed
dmarcs opened this issue Nov 22, 2021 · 0 comments · Fixed by #1450
Closed

Allow array values for extra #1451

dmarcs opened this issue Nov 22, 2021 · 0 comments · Fixed by #1450
Labels
enhancement New feature or request logstash

Comments

@dmarcs
Copy link
Contributor

dmarcs commented Nov 22, 2021

Chart version:
7.15.10

Kubernetes version:
v1.21.5

Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
Docker for Mac

Helm Version:
v3.3.4

helm get release output

e.g. helm get elasticsearch (replace elasticsearch with the name of your helm release)

Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting.

If you find some secrets in plain text in helm get release output you should use Kubernetes Secrets to managed them is a secure way (see Security Example).

Output of helm get release

Describe the bug:
According to https://github.com/elastic/helm-charts/blob/main/logstash/values.yaml this should work

extraVolumes:
  - name: extras
     emptyDir: {}

extraVolumeMounts:
  - name: extras
     mountPath: /usr/share/extras
     readOnly: true

but I get this error when I run helm install

Error: template: charts/logstash/templates/statefulset.yaml:143:14: executing "charts/logstash/templates/statefulset.yaml" at <.Values.extraVolumes>: wrong type for value; expected string; got []interface {}

Steps to reproduce:

  1. Set extraVolumes and extraVolumeMounts
extraVolumes:
  - name: extras
     emptyDir: {}

extraVolumeMounts:
  - name: extras
     mountPath: /usr/share/extras
     readOnly: true
  1. helm install logstash

Expected behavior:
Volume should be created, but instead there's an error message

Provide logs and/or server output (if relevant):

Be careful to obfuscate every secrets (credentials, token, public IP, ...) that could be visible in the output before copy-pasting

Any additional context:
Issue is fixed with with #1450

@framsouza framsouza added the enhancement New feature or request label Nov 22, 2021
@jmlrt jmlrt added logstash bug Something isn't working and removed enhancement New feature or request labels Feb 2, 2022
@jmlrt jmlrt added enhancement New feature or request and removed bug Something isn't working labels Feb 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request logstash
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants