pires / kubernetes-elasticsearch-cluster

Elasticsearch cluster on top of Kubernetes made easy.
Apache License 2.0
1.51k stars 690 forks source link

[Help request] Kibana official images #163

Closed Unb6rn closed 6 years ago

Unb6rn commented 6 years ago

Hello! I am trying to make this all work with original docker images from elastic docker repo. It was not so hard to make elastic up and running, because pires left all the dockerfiles and configs for his customised images here oh GitHub. But kibana deployment uses some kind of customised images with dockerfiles nowhere to be found. So, the question is-how does the Kibana know where to connect? There is no such variable in yaml, so I assume, some kind of discovery should be in the image. Thanks!

selangley commented 6 years ago

I modified my kibana.yaml to use:

image: docker.elastic.co/kibana/kibana-oss:6.1.1

where kibana-oss is the version of Kibana that Elastic has made available without X-Pack included.

Then you need to remove the name value pairs that disable the X-Pack features from your kibana.yml because those plugins are no longer there.

pires commented 6 years ago

Feel free to open a PR that updates the Kibana part.

karlskewes commented 6 years ago

@Unb0rn Pires has recently accepted my pull request to update to Kibana OSS image. Kibana connects to Elastic Search through standard (ES standard) ports.

Try pull the latest and see how you get on.

Just note that for the kibana service exposes kibana on port 80. In my own setup I kept everything on standard ES ports (ie: kibana 5601) and ran a nginx proxy in front.