# Unsetup cross site replication with Percona MongoDB Operator

**URL:** <https://forums.percona.com/t/unsetup-cross-site-replication-with-percona-mongodb-operator/31189>\
**Category:** Percona Operator for MongoDB\
**Created:** [June 24, 2024, 7:46am UTC](https://forums.percona.com/t/unsetup-cross-site-replication-with-percona-mongodb-operator/31189 "2024-06-24T07:46:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adlk](https://avatars.discourse-cdn.com/v4/letter/a/58f4c7/32.png) [@adlk](https://forums.percona.com/u/adlk)\
**Post date:** [June 24, 2024, 7:46am UTC](https://forums.percona.com/t/unsetup-cross-site-replication-with-percona-mongodb-operator/31189/1 "2024-06-24T07:46:22Z")

</div>

ephrase this forums post: Hi everyone,

I’m currently evaluating the Percona MongoDB Kubernetes Operator (v1.16), with a particular focus on cross-site replication. I’ve been struggling to set up the instances for the passive site. The main issues I’ve encountered are:

- The secrets copied from the active site get overwritten by the operator.
- The instances never reach a ready state.

Has anyone else faced similar challenges? If so, could you share any tips or best practices for successfully setting up the passive instance?

Thanks in advance for your help!

---

<div class="post-metadata">

**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\
**Post date:** [June 24, 2024, 7:56am UTC](https://forums.percona.com/t/unsetup-cross-site-replication-with-percona-mongodb-operator/31189/2 "2024-06-24T07:56:33Z")

</div>

@adlk it might be quite challenging to set it up, as it requires secret copy and precise configuration on both ends (especially on the “replica” side).

Could you please share your YAML manifests?

If your secrets are rewritten, it might be that you are facing a bug from 1.16.0.  
[https://perconadev.atlassian.net/browse/K8SPSMDB-1101](https://perconadev.atlassian.net/browse/K8SPSMDB-1101)

The release of 1.16.1 is today that addresses this bug.
