[Kibana] 8.5.1"message":"secrets \"kibana-kibana-es-token\" already exists"

[JoranDox]

[Kibana] 8.5.1"message":"secrets \"kibana-kibana-es-token\" already exists"

[nattawitc]

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

          return requestPromise(k8sDeleteSecretUrl, secretDeleteOptions, {extraStatusCode: 404}).then(() => {
            return requestPromise(k8sPostSecretUrl, secretCreateOptions, {payload: secretData})
          })

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.

[bcouetil]

Hello, came here to solve this annoying issue when upgrading.

Thanks for the tips to delete the token.

Will there be any fix soon ?

[doverk96]

@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 ?

[djerfy]

Hello, same problem here (with ArgoCD). With Helm, you can upgrade with --no-hooks option