# Secret Management

**URL:** <https://discuss.elastic.co/t/secret-management/296171>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [February 3, 2022, 10:03am UTC](https://discuss.elastic.co/t/secret-management/296171 "2022-02-03T10:03:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vishnu\_Kadavarath\_Vi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishnu_kadavarath_vi/32/101297_2.png) [@Vishnu\_Kadavarath\_Vi](https://discuss.elastic.co/u/Vishnu_Kadavarath_Vi)\
**Post date:** [February 3, 2022, 10:03am UTC](https://discuss.elastic.co/t/secret-management/296171/1 "2022-02-03T10:03:27Z")

</div>

HI guys,  
I wanted to know if there is any way of adding custom annotations to APM/Elasticsearch secrets in ECK.  
I.E adding reflector annotations to APM/Elasticsearch certs and APM/Elasticsearch user-token. So that it can be replicated to multiple namespaces

Regards,  
Vishnu

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [February 7, 2022, 9:58am UTC](https://discuss.elastic.co/t/secret-management/296171/2 "2022-02-07T09:58:58Z")

</div>

If you are referring to the secrets generated internally by the ECK operator then there is currently no way to add additional metadata I am afraid.

---

<div class="post-metadata">

**Author:** ![Vishnu\_Kadavarath\_Vi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishnu_kadavarath_vi/32/101297_2.png) [@Vishnu\_Kadavarath\_Vi](https://discuss.elastic.co/u/Vishnu_Kadavarath_Vi)\
**Post date:** [February 19, 2022, 9:15am UTC](https://discuss.elastic.co/t/secret-management/296171/3 "2022-02-19T09:15:02Z")

</div>

Yes, the secrets generated by ECK operator.  
Is there any possibility of adding that functionality in future releases. This would be helpful

---

<div class="post-metadata">

**Author:** ![Michael\_Montgomery](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_montgomery/32/82242_2.png) [@Michael\_Montgomery](https://discuss.elastic.co/u/Michael_Montgomery)\
**Post date:** [February 22, 2022, 3:04pm UTC](https://discuss.elastic.co/t/secret-management/296171/4 "2022-02-22T15:04:19Z")

</div>

Would you mind opening an issue [Issues · elastic/cloud-on-k8s · GitHub](https://github.com/elastic/cloud-on-k8s/issues) so we could discuss, and prioritize? Thank you.

---

<div class="post-metadata">

**Author:** ![Vishnu\_Kadavarath\_Vi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishnu_kadavarath_vi/32/101297_2.png) [@Vishnu\_Kadavarath\_Vi](https://discuss.elastic.co/u/Vishnu_Kadavarath_Vi)\
**Post date:** [March 15, 2022, 8:06am UTC](https://discuss.elastic.co/t/secret-management/296171/5 "2022-03-15T08:06:13Z")

</div>

Yes, i have opened the issue in this [link](https://github.com/elastic/cloud-on-k8s/issues/5474)

---

<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 12, 2022, 8:06am UTC](https://discuss.elastic.co/t/secret-management/296171/6 "2022-04-12T08:06:36Z")

</div>

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