# Elastic search with XPack on Azure K8S **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-security, docker\ **Created:** [November 20, 2019, 6:50am UTC](https://discuss.elastic.co/t/elastic-search-with-xpack-on-azure-k8s/208628 "2019-11-20T06:50:46Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![siddheshb](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@siddheshb](https://discuss.elastic.co/u/siddheshb)\ **Post date:** [November 20, 2019, 6:50am UTC](https://discuss.elastic.co/t/elastic-search-with-xpack-on-azure-k8s/208628/1 "2019-11-20T06:50:46Z")
I have few queries regarding setting up ES on kubernetes as we are currently facing issues while enabling basic security in our 3 master, 2 data and 2 client node configuration 1. Is the helm chart stable/elasticsearch supported for version 6.8.4 or 7.4.2? 2. How can we leverage the user authentication available as a part of basic license by setting Xpack. enabled: true option? Currently using the default settings ( 3 master and 2 data nodes and 2 client), we are not able to get either pods in ready state. On disabling the xpack.enabled option, everything works as normal. 3. Are there any other settings apart from xpack.enabled: true, to allow the statefulsets to function as expected? 4. Is there a provision to allow the inbuilt user secrets created using Kubernetes secrets? How can we ensure that the values of these secrets are known to ES administrators? 5. In case I want to replace the existing chart with elastic’s helm chart (as mentioned in the pre deprecation notice), how can we make sure to deploy the data nodes? Currently I am not able to see a stateful set for data nodes or any configuration. ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [November 20, 2019, 6:55am UTC](https://discuss.elastic.co/t/elastic-search-with-xpack-on-azure-k8s/208628/2 "2019-11-20T06:55:20Z")
Hi @siddheshb, please refrain from opening multiple duplicate posts for your question. Can you please either delete/close this one or [Elasticsearch on Kubernetes with helm](https://discuss.elastic.co/t/elasticsearch-on-kubernetes-with-helm/208627/2) ? ---
**Author:** ![siddheshb](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@siddheshb](https://discuss.elastic.co/u/siddheshb)\ **Post date:** [November 20, 2019, 7:03am UTC](https://discuss.elastic.co/t/elastic-search-with-xpack-on-azure-k8s/208628/3 "2019-11-20T07:03:59Z")
Hello @ikakavas Please let me know if the this question needs to be answered as a part of Elastic group or Infrastructure group. Will close the irrelevant call Thanks Sid ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [November 20, 2019, 8:09am UTC](https://discuss.elastic.co/t/elastic-search-with-xpack-on-azure-k8s/208628/4 "2019-11-20T08:09:20Z")
As you can see in [Metrics - Discuss the Elastic Stack](https://discuss.elastic.co/c/infrastructure), this is about : > Everything related to the Infrastructure app – Filebeat and Metricbeat, modules, Kibana dashboards, and using the Kibana Infrastructure app. So I think your question is better suited here, I added the appropriate tags ---
**Author:** ![siddheshb](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@siddheshb](https://discuss.elastic.co/u/siddheshb)\ **Post date:** [November 22, 2019, 6:07am UTC](https://discuss.elastic.co/t/elastic-search-with-xpack-on-azure-k8s/208628/5 "2019-11-22T06:07:02Z")
Hello All, Any update on this? Thanks ---
**Author:** ![Julien\_MAILLERET](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/julien_mailleret/32/45074_2.png) [@Julien\_MAILLERET](https://discuss.elastic.co/u/Julien_MAILLERET)\ **Post date:** [November 27, 2019, 10:44am UTC](https://discuss.elastic.co/t/elastic-search-with-xpack-on-azure-k8s/208628/6 "2019-11-27T10:44:39Z")
Hi @siddheshb, [https://github.com/helm/charts/tree/master/stable/elasticsearch](https://github.com/helm/charts/tree/master/stable/elasticsearch) isn't managed by Elastic. You should address your questions about this chart to [https://github.com/helm/charts/issues](https://github.com/helm/charts/issues). [https://github.com/elastic/helm-charts/tree/master/elasticsearch](https://github.com/elastic/helm-charts/tree/master/elasticsearch) is the one supported by Elastic. It has just been tested and updated for 6.8.5 and 7.4.2 ([elasticsearch#compatibility](https://github.com/elastic/helm-charts/tree/master/elasticsearch#compatibility)). 7.4.2 is the default version deployed by helm chart, you can deploy another version by setting `imageTag` value (example: `helm install --name elasticsearch elastic/elasticsearch --set imageTag=6.8.5`). You can find an example of deploying Elasticsearch with authentication using Elastic helm chart in [helm-charts/elasticsearch/examples/security](https://github.com/elastic/helm-charts/tree/master/elasticsearch/examples/security). With Elastic helm chart, each group of node is deployed separately in a different chart release. You can find an example with migration from stable/elasticsearch chart instruction in [helm-charts/elasticsearch/examples/migration](https://github.com/elastic/helm-charts/tree/master/elasticsearch/examples/migration). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 25, 2019, 10:44am UTC](https://discuss.elastic.co/t/elastic-search-with-xpack-on-azure-k8s/208628/7 "2019-12-25T10:44:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.