Kibana server.uuid and server.name configs
See original GitHub issueChart 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.
Issue Analytics
- State:
- Created 3 years ago
- Comments:17 (5 by maintainers)
Top Results From Across the Web
Configure Kibana | Kibana Guide [8.5] - Elastic
A reference of the reporting settings administrators configure in kibana.yml. ... The Kibana server reads properties from the kibana.yml file on startup.
Read more >Kibana says "Kibana server is not ready yet ... - Stack Overflow
I'm trying to start over, so I shelled into the Elasticsearch instance and ran elasticsearch-reset-password --username elastic . I saw the ...
Read more >Forbidden after start autorefresh in canvas - Users Feedback
My kibana config: server.name: kibana. server.host: 0.0.0.0. elasticsearch.hosts: [ “http://elasticsearch:9200” ].
Read more >Provision Grafana | Grafana documentation
Describes provisioning settings for Grafana using configuration files. ... Controls the server name used for certificate common name/subject alternative ...
Read more >Configuration - Gerrit Code Review
In this configuration the web server is not involved in the user authentication ... groups by group UUID, including the group owner, name,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We addressed this adding some extraEnvs:
This would set
SERVER_NAME
to the current pod name and SERVER_UUID to the pod uuid. Of course this doesn’t persist the name or uuid through pod restarts/deployments. But I don’t think it has to.Does anyone see a problem doing it this way?
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.