elasticsearch-client | client exposes the Elasticsearch Java High Level | Application Framework library

As @David Maze pointed out I should put the (bootstrap) password into a secret.

My initial problem was that I thought that the elasticsearch-setup-passwords tool was the only way to set up the (user) password.

In other words, I did not know the password before the program was started. But I just found a way to change the bootstrap password beforehand here, so the problem is solved.

The reason why pod is pending is below PVCs are pending because corresponding PVs are not created.

You have not declared your grgit variable.

You can get a Grgit instance by:

This is because one of your dependencies is trying to access the Event object, which is not available by default server side.

Since you are already using domino, you can try adding these lines to your server.ts to make Event object available

The values.yaml file is not evaluated. So you cannot use {{ .Release.Name }} inside values.yaml.

The reason why it works for ELASTICSEARCH_HOSTS is that inside Kibana Helm Chart, the values are first kind-of copied and later evaluated.

Finally we found the problem. One developer created a template with index match like index_patterns: ['*'] And it broke kibana monitoring.

Workaround provided by AmazingTurtle:

I enabled DNS by creating these three manifests manually

• kube-dns-cm.yaml
• kube-dns-controller.yaml
• kube-dns-svc.yaml

Just did kubectl apply -f for all the three items

Update:

The mentioned files was deleted by the PR#3332 from the master branch, so I've changed the links to the last commit that contains them.

I found the issue.

The Elasticsearch Client TransportClient that spring-boot-starter-data-elasticsearch autoconfigures is deprecated. It gets auto configured by and needs to connect to the 9300 "transport" API. But this is a headless service for internal Kubernetes discovery and there's no way of exposing it.

So, I've switched to the newer RestHighLevelClient: https://www.elastic.co/guide/en/elasticsearch/client/java-rest/6.3/java-rest-high.html

Also, I needed to disable this management.health.elasticsearch.enabled=false since it was trying to connect to an elasticsearh on localhost??

I just need to figure out if RestHighLevelClient can be used by spring-data ElasticsearchRepository

I tried this myself and there's something with the Kibana docker image and/or Helm chart on how the parameter is passed into Kibana. Basically, the command line shows: