# MongoDB operator creates/overwrites "external" secret by it self

**URL:** <https://forums.percona.com/t/mongodb-operator-creates-overwrites-external-secret-by-it-self/14794>\
**Category:** Percona Operator for MongoDB\
**Created:** [March 18, 2022, 6:27am UTC](https://forums.percona.com/t/mongodb-operator-creates-overwrites-external-secret-by-it-self/14794 "2022-03-18T06:27:05Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![rdxmbr](https://avatars.discourse-cdn.com/v4/letter/r/c2a13f/32.png) [@rdxmbr](https://forums.percona.com/u/rdxmbr)\
**Post date:** [October 30, 2023, 3:44pm UTC](https://forums.percona.com/t/mongodb-operator-creates-overwrites-external-secret-by-it-self/14794/5 "2023-10-30T15:44:43Z")

</div>

seems we have a similiar problem with creating the tls-certs: [Is it possible to rotate MongoDB user/password without interrupting the operator?](https://forums.percona.com/t/is-it-possible-to-rotate-mongodb-user-password-without-interrupting-the-operator/26252)

> I assume the desire here is the following behavior for the situation when secret is specified in cr.yaml:
> 
> ```
> Operator checks if secret is in k8s
> if not - it waits for it (checks every reconcile loop)
> 
> ```

👍

---

_[View the full topic](https://forums.percona.com/t/mongodb-operator-creates-overwrites-external-secret-by-it-self/14794)._