<p>I am trying to deploy production grade Elasticsearch 6.3.0 on Kubernetes.</p>
<p>Came across few articles, but still not sure what is the best approach to go with.</p>
<ol>
<li><a href="https://github.com/pires/kubernetes-elasticsearch-cluster" rel="nofollow noreferrer">https://github.com/pires/kubernetes-elasticsearch-cluster</a></li>
</ol>
<p>It doesn't use stateful set.</p>
<ol start="2">
<li><a href="https://anchormen.nl/blog/big-data-services/elastic-search-deployment-kubernetes/" rel="nofollow noreferrer">https://anchormen.nl/blog/big-data-services/elastic-search-deployment-kubernetes/</a></li>
</ol>
<p>This is pretty old.</p>
<p>Using elastic search for App search.</p>
<p>Images from Elasticsearch are</p>
<pre><code>docker pull docker.elastic.co/elasticsearch/elasticsearch:6.3.0
docker pull docker.elastic.co/elasticsearch/elasticsearch-oss:6.3.0
</code></pre>
<p>I would like to go with -oss image and it is the core Apache one.</p>
<p>Is there any good documentation on setting up production grade 6.3.0 version on Kubernetes.</p>

<p>One of the most promising new developments for running Elasticearch on Kubernetes is the <a href="https://github.com/upmc-enterprises/elasticsearch-operator" rel="nofollow noreferrer">Elasticsearch Operator</a>.</p>

<p>Kubernetes <a href="https://coreos.com/operators/" rel="nofollow noreferrer">Operators</a> allow for more sophistication when it comes to dealing with the requirements of complex tools (and Elasticsearch is definitely one). Especially when considering the need to avoid losing Elasticsearch data, an operator is the way to go.</p>
