Chart version: 7.9.2
Kubernetes version: 1.16.8
Kubernetes provider: Rancher
Helm Version: 3.2.4
Describe the bug: According to this doc from Elastic, the following configs need to be unique for kibana installations being served from behind a load balancer:
server.uuid
server.name
The chart in this repo does not specify how these values can be set for kibana installations that use this chart.
Hi @ilhaan,
These settings should be defined in kibana.yml config files.
You can use kibanaConfig value for that:
kibanaConfig:
kibana.yml:
server.uuid: <uuid>
server.name: <name>
We recommend submitting these kind of questions on https://discuss.elastic.co forum where you have more chances to get answers and advices.
Hi @jmlrt,
Thanks for the response. Defining these in the chart would mean all Kibana pods would have the same uuid and name. That seems to counter what is listed in documentation here:
Settings unique across each Kibana instance:
server.uuid server.namePlease advise. Will post in forum as well.
That's a good point.
I don't see how to do it currently, I'll reopen the issue.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has not been resolved so it should not be marked stale.
@jmlrt any updates on this? We upgraded ES and Kibana to 7.11 today we see the following when we launch multiple kibana pods:
"type":"log","@timestamp":"2021-02-16T19:35:56+00:00","tags":["warning","savedobjects-service"],"pid":7,"message":"Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_task_manager_7 and restarting Kibana."}
Hi @ilhaan, unfortunately no we don't have time to work on that currently.