The follow option: https://www.mongodb.com/docs/kubernetes-operator/master/reference/k8s-operator-specification/#spec.externalAccess.externalDomain - spec.externalAccess.externalDomain Is tremendously useful as we would no longer have to worry about terminating TLS connections through a proxy and then re-establishing a TLS connection for internal communication due to security reasons. This would remove a point of failure for self-hosted Kubernetes environments and safe resources. However, you cannot do this for existing replica sets: WARNING > Specifying this field changes how Ops Manager registers mongod processes. You can specify this field only for new replica set deployments starting in Kubernetes Operator version 1.19. You can’t change the value of this field or any processes[n].hostname fields in the Ops Manager automation configuration for a running replica set deployment. Is there any way to enable this setting for running replica sets? If not then this would basically force everyone who wants to try this option to transfer all their instances to new replica sets which is a huge doing from the customer's side, especially if you are running a large amount of deployments on K8s already.