Add support for cerebro

clockworksoul / helm-elasticsearch

An Elasticsearch cluster on top of Kubernetes, made easier, with Helm.

Apache License 2.0

118 stars 76 forks source link

Closed jjungnickel closed 6 years ago

andrey-moor commented 6 years ago

I'd keep it more or less synced up with https://github.com/pires/kubernetes-elasticsearch-cluster. Can you create similar PR there as well?

@clockworksoul your thoughts?

jjungnickel commented 6 years ago

@andrey-moor Yeah, I guess that makes sense

clockworksoul commented 6 years ago

I agree. I don't think the goal needs to be 1:1 exact, but we should keep in sync where we can.

jalberto commented 6 years ago

Cerebro does not follow Elastic release cycles, and is designed as a isolated client, so one cerebro can access every ES cluster.

i suggest to keep cerebro as a separated helm

sagikazarmark commented 6 years ago

Sounds reasonable

jjungnickel commented 6 years ago

I agree!