Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/elastic-stack] Not possible to modify elastic url in Kibana config #14445

Closed
alb3rtobr opened this issue Jun 4, 2019 · 2 comments
Closed
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@alb3rtobr
Copy link

Describe the bug
Kibana configuration does not use the elastic url provided in the values.yaml

Version of Helm and Kubernetes:

$ helm version
Client: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.0", GitCommit:"79d07943b03aea2b76c12644b4b54733bc5958d6", GitTreeState:"clean"}

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.0", GitCommit:"641856db18352033a0d96dbc99153fa3b27298e5", GitTreeState:"clean", BuildDate:"2019-03-25T15:53:57Z", GoVersion:"go1.12.1", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T16:14:56Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
elastic-stack

What happened:
It is not possible to change the elastic url in the Kibana configuration. This is the kibana section in the values.yaml :

kibana:
 enabled: true
 env:
ELASTICSEARCH_URL: http://http.default.svc.cluster.local:9200

Kibana was not starting, and in the pod logs I found it trying to connect to a wrong url:

{"type":"log","@timestamp":"2019-06-04T10:24:25Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}

Also, the first line of the log is the following:

{"type":"log","@timestamp":"2019-06-04T10:24:01Z","tags":["warning","elasticsearch","config","deprecation"],"pid":1,"message":"Config key \"url\" is deprecated. It has been replaced with \"hosts\""}

I found out that in Kibana 6.6, the config parameter ELASTICSEARCH_URL changed to ELASTICSEARCH_HOSTS. And Im using 6.7

The kibana chart shows the change:

env: {}
  ## All Kibana configuration options are adjustable via env vars.
  ## To adjust a config option to an env var uppercase + replace `.` with `_`
  ## Ref: https://www.elastic.co/guide/en/kibana/current/settings.html
  ## For kibana < 6.6, use ELASTICSEARCH_URL instead
  # ELASTICSEARCH_HOSTS: http://elasticsearch-client:9200
  # SERVER_PORT: 5601
  # LOGGING_VERBOSE: "true"
  # SERVER_DEFAULTROUTE: "/app/kibana"

files:
  kibana.yml:
    ## Default Kibana configuration from kibana-docker.
    server.name: kibana
    server.host: "0"
    ## For kibana < 6.6, use elasticsearch.url instead
elasticsearch.hosts: http://elasticsearch:9200

What you expected to happen:
Kibana should be configured using ELASTICSEARCH_HOSTS.

How to reproduce it (as minimally and precisely as possible):
Just try to install the chart as described in the instructions. Kibana will not start properly.

Thanks in advance!

@alb3rtobr alb3rtobr changed the title [elastic-stack] Not possible to modify elastic url in Kibana config [stable/elastic-stack] Not possible to modify elastic url in Kibana config Jun 6, 2019
@stale
Copy link

stale bot commented Jul 6, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 6, 2019
@stale
Copy link

stale bot commented Jul 20, 2019

This issue is being automatically closed due to inactivity.

@stale stale bot closed this as completed Jul 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant