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.
Maybe the instructions here should be updated to ask for helm get all ${releasename}, because it was really unclear what to do, and that release was the name of a release and not a keyword.
Describe the bug: helm upgrade --install kibana elastic/kibana works only once, updating kibana doesn't work
Steps to reproduce:
helm upgrade --install elastic elastic/elastic # elastic works
helm upgrade --install kibana elastic/kibana # now kibana works, connected to elastic, all fine
helm upgrade --install kibana elastic/kibana # times out, and there's a bunch of pods named pre-install-kibana-kibana-XXXXX all in the erred state
Expected behavior: helm upgrade --install just works and applies new values if relevant
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
kubectl logs pre-install-kibana-kibana-26xrr
Creating a new Elasticsearch token for Kibana
Cleaning previous token
statusCode: 200
Creating new token
statusCode: 200
Creating K8S secret
statusCode: 409
{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"secrets \"kibana-kibana-es-token\" already exists","reason":"AlreadyExists","details":{"name":"kibana-kibana-es-token","kind":"secrets"},"code":409}
Any additional context:
Looks like it can't handle the token already existing? I see code claiming to clean the token, but I guess that's not working.
Possibly related to #1765 but they didn't add enough output to be sure, so I don't want to assume it's the same issue.
The text was updated successfully, but these errors were encountered:
I see code claiming to clean the token, but I guess that's not working.
It's working but that's the part where it remove the old token from elasticsearch not from k8s cluster.
The actual problem is from line below where it make a post request to k8s to create a secret. The quick fix is to remove the old secret first
That fix the initial problem but it still doesn't work seamlessly if the update doesn't change the deployment. Its pods will not restart and will use the old token. You'll still need to manually restart the deployment.
@JoranDox Tried installing the Kibana post Elasticsearch deployment but it fails saying cannot use elastic username as it is a superuser. Any help ? how can we create a user for Kibana so that pre install job gets succeeded ?
Chart version:
8.5.1
Kubernetes version:
GitVersion:"v1.23.8"
Kubernetes provider:
Azure AKS
Helm Version:
Version:"v3.10.3"
helm get release
outputMaybe the instructions here should be updated to ask for
helm get all ${releasename}
, because it was really unclear what to do, and thatrelease
was the name of a release and not a keyword.Output of helm get release
Describe the bug:
helm upgrade --install kibana elastic/kibana
works only once, updating kibana doesn't workSteps to reproduce:
helm upgrade --install elastic elastic/elastic
# elastic workshelm upgrade --install kibana elastic/kibana
# now kibana works, connected to elastic, all finehelm upgrade --install kibana elastic/kibana
# times out, and there's a bunch of pods named pre-install-kibana-kibana-XXXXX all in theerred
stateExpected behavior:
helm upgrade --install
just works and applies new values if relevantProvide 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
kubectl logs pre-install-kibana-kibana-26xrr
Any additional context:
Looks like it can't handle the token already existing? I see code claiming to clean the token, but I guess that's not working.
Possibly related to #1765 but they didn't add enough output to be sure, so I don't want to assume it's the same issue.
The text was updated successfully, but these errors were encountered: