# Credentials for elastic-operator

**URL:** <https://discuss.elastic.co/t/credentials-for-elastic-operator/212628>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Tags:** elastic-stack-security\
**Created:** [December 20, 2019, 8:39am UTC](https://discuss.elastic.co/t/credentials-for-elastic-operator/212628 "2019-12-20T08:39:25Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![charith-elastic](https://avatars.discourse-cdn.com/v4/letter/c/3ec8ea/32.png) [@charith-elastic](https://discuss.elastic.co/u/charith-elastic)\
**Post date:** [December 23, 2019, 1:52pm UTC](https://discuss.elastic.co/t/credentials-for-elastic-operator/212628/9 "2019-12-23T13:52:40Z")

</div>

Hi,

You don't need the owner reference. If the `[cluster]-es-internal-users` secret exists with the correct entries in the `data` section, ECK will use that secret.

```auto
kubectl create secret generic quickstart-es-internal-users --from-literal=elastic-internal-probe=probepasswd --from-literal=elastic-internal=internalpasswd --from-literal=elastic-internal-keystore=keystorepasswd

```

Because secrets are mounted as read-only volumes, I doubt the `elasticsearch-users` tool can be used but I have not tried to use it that way and can't give you a definite answer.

---

_[View the full topic](https://discuss.elastic.co/t/credentials-for-elastic-operator/212628)._