-
Notifications
You must be signed in to change notification settings - Fork 1.9k
elastisearch 8.1.0 - helm error #1626
Comments
Please can you double check the vaues.yaml content? |
please help i am not much familliar with elasticsearch to host into kubernetes. |
Please use stackoverflow to ask help, github issue is for bugs or feature requests. You are using Helm chart elasticsearch, version 7.17.1, values.yaml "syntax" is here : https://github.com/elastic/helm-charts/blob/v7.17.1/elasticsearch/values.yaml#L11 Dont use values.yaml from master branch! |
@ebuildy still the same, |
hello, helm-chart version 8 it's not ready yet. we are working on it (no ETA) and for now the last helm-chart available is 7.17.1 as you can see here |
Having different versions of the Helm chart in the repository and in the GIT master is very confusing. Please get rid of it in the future. |
I just upgraded from 7.17.1 to 8.1.0. Now facing a similar issue. The big concern is when I try to revert back to version 7.17.1, this time, I can't go back as the error says there is already a version moved on 8.1.0 (usr/share/elasticsearch/data) file has version maintained. |
8.1.0 is still not supported. see #1594 |
Chart version:
7.17.1
Kubernetes version:
v1.20
Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
Alicloud
Helm Version:
v3.7.2
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:
Steps to reproduce:
Expected behavior:
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:
The text was updated successfully, but these errors were encountered: