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
{{ message }}
This repository has been archived by the owner on May 16, 2023. It is now read-only.
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
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
outpute.g.
helm get elasticsearch
(replaceelasticsearch
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 workbut I get this error when I run
helm install
Steps to reproduce:
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
The text was updated successfully, but these errors were encountered: