# Setting custom name for Replica Set Config Server

**URL:** <https://forums.percona.com/t/setting-custom-name-for-replica-set-config-server/18082>\
**Category:** Percona Operator for MongoDB\
**Created:** [October 19, 2022, 9:08am UTC](https://forums.percona.com/t/setting-custom-name-for-replica-set-config-server/18082 "2022-10-19T09:08:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kamuna](https://avatars.discourse-cdn.com/v4/letter/k/839c29/32.png) [@kamuna](https://forums.percona.com/u/kamuna)\
**Post date:** [October 19, 2022, 9:08am UTC](https://forums.percona.com/t/setting-custom-name-for-replica-set-config-server/18082/1 "2022-10-19T09:08:02Z")

</div>

How to set a custom name for Replica Set Config Server?  
The default is “cfg”  
I tried this option, but it did not work.

```auto
  sharding:
    enabled: true
    configsvrReplSet:
      size: 3
      configuration: |
        replication:
          replSetName: myCustomName

```

Is this not possible at all as noted here?

> <https://github.com/percona/percona-server-mongodb-operator/blob/e00b8902287ebd20a7a1b13097d1cf3c1b164186/pkg/apis/psmdb/v1/psmdb_defaults.go#L31>

I would like to migrate the existing selfhosted Mongodb to Kubernetes and try to use this procedure:

> **[Migrating MongoDB to Kubernetes - Percona Database Performance Blog](https://www.percona.com/blog/migrating-mongodb-to-kubernetes)**
>
> Migrating MongoDB to Kubernetes is a challenging task, but it is much simpler with Percona Distribution for MongoDB Operator.

The config replica set name on the source MongoDB is not “cfg”.  
Is renaming the config replica set to “cfg” on the source MongoDB the only way to do this?

---

<div class="post-metadata">

**Author:** ![Tomislav\_Plavcic](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/tomislav_plavcic/32/9717_2.png) [@Tomislav\_Plavcic](https://forums.percona.com/u/Tomislav_Plavcic)\
**Post date:** [October 19, 2022, 12:06pm UTC](https://forums.percona.com/t/setting-custom-name-for-replica-set-config-server/18082/2 "2022-10-19T12:06:55Z")

</div>

Hi @kamuna !  
I believe currently it is not possible with the procedure you linked. What comes into mind is maybe doing a logical backup then renaming the replica inside it, but that could be messy even if possible.

I would encourage you to open a Jira ticket here: [https://jira.percona.com/](https://jira.percona.com/) under project: `K8SPSMDB` and describe your use case so it will be considered for some future release (from what I see it should not be hard to implement).

---

<div class="post-metadata">

**Author:** ![kamuna](https://avatars.discourse-cdn.com/v4/letter/k/839c29/32.png) [@kamuna](https://forums.percona.com/u/kamuna)\
**Post date:** [October 28, 2022, 5:09am UTC](https://forums.percona.com/t/setting-custom-name-for-replica-set-config-server/18082/3 "2022-10-28T05:09:53Z")

</div>

[https://jira.percona.com/browse/K8SPSMDB-807](https://jira.percona.com/browse/K8SPSMDB-807)