After patching the cluster with `spec.sharding.enabled: false`, config server and mongos objects are deleted but PBM still tries to connect to config servers because it still sees the cluster as sharded.
If you want to disable sharding in a running cluster, you need to pause cluster first. As we found out in , PBM can’t handle enabling/disabling of sharding in a rolling fashion.
After patching the cluster with `spec.sharding.enabled: false`, config server and mongos objects are deleted but PBM still tries to connect to config servers because it still sees the cluster as sharded.