# Elasticsearch security with a multiple Helm charts cluster

**URL:** <https://discuss.elastic.co/t/elasticsearch-security-with-a-multiple-helm-charts-cluster/268081>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [March 23, 2021, 11:08am UTC](https://discuss.elastic.co/t/elasticsearch-security-with-a-multiple-helm-charts-cluster/268081 "2021-03-23T11:08:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [March 23, 2021, 11:08am UTC](https://discuss.elastic.co/t/elasticsearch-security-with-a-multiple-helm-charts-cluster/268081/1 "2021-03-23T11:08:13Z")

</div>

We are running elasticsearch on kubernetes, via official elastic Helm chart. As per elastic recommandation, we run 3 Helm releases with dedicated role:

- master
- data
- client

Usually, I deploy master release first, then data, end client.

Now we have a gold licence, so to apply it I must setup security: TLS communication and authentication.

TLS seems fine (I use an initContainer to create cert for each container).

Now, I am trying to deploy the master release (only master nodes), but I got this error:

**UnavailableShardsException: at least one primary shard for the index [.security-7] is unavailable**

I guess ES need data nodes to store this data, so it cannot start master nodes, which is required to start data nodes !

What should be the process here?

---

<div class="post-metadata">

**Author:** ![ebuildy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ebuildy/32/6070_2.png) [@ebuildy](https://discuss.elastic.co/u/ebuildy)\
**Post date:** [March 23, 2021, 1:24pm UTC](https://discuss.elastic.co/t/elasticsearch-security-with-a-multiple-helm-charts-cluster/268081/2 "2021-03-23T13:24:14Z")

</div>

The only solution I have found , is to declare an anonymous user:

```auto
      xpack.security.authc:
        anonymous:
          username: anonymous 
          roles: superuser
          authz_exception: true 

```

I will configure user later, once all nodes are up and ready.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [April 20, 2021, 1:24pm UTC](https://discuss.elastic.co/t/elasticsearch-security-with-a-multiple-helm-charts-cluster/268081/3 "2021-04-20T13:24:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.