Verify the cluster operation¶

Give the cluster a few minutes to initialize. Once kubectl get psmdb -n <namespace> shows the status as ready, you can connect to the database.

To connect to Percona Server for MongoDB, use the connection string Secret that the Operator creates for the databaseAdmin user. This Secret is available starting with Operator version 1.23.0 and newer. For previous versions, refer to the Connect manually section.

List the Secrets objects:
```
kubectl get secrets -n <namespace>
```
The connection string Secret is named my-cluster-name-databaseadmin-conn-str by default.

Retrieve the connection string

Sharding is onSharding is off

kubectl get secret <clusterName>-databaseadmin-conn-str -n <namespace> \
 -o jsonpath='{.data.databaseAdmin_mongos_connectionString}' | base64 --decode && echo

kubectl get secret <clusterName>-databaseadmin-conn-str -n <namespace> \
-o jsonpath='{.data.databaseAdmin_rs0_connectionStringSrv}' | base64 --decode && echo

See Connection secrets for other available keys.

Run a container with a MongoDB client and connect its console output to your terminal. The following command does this, naming the new Pod percona-client:
```
kubectl run -i --rm --tty percona-client --image=percona/percona-server-mongodb:8.0.26-11 --restart=Never -- bash -il
```
Executing it may require some time to deploy the corresponding Pod.
Connect using the connection string from step 2:
```
mongosh "<connection-string>"
```

Connect manually (alternative)¶

If you need to build a connection URI yourself, retrieve credentials from the user Secret and construct the URI.

List the Secrets objects:
```
kubectl get secrets -n <namespace>
```
The Secrets object you are interested in has the <cluster-name>-secrets name. (For the cluster my-cluster-name, the Secret name is my-cluster-name-secrets).

Retrieve the admin username and password:

kubectl get secret <secret-name> -n <namespace> -o jsonpath='{.data.MONGODB_DATABASE_ADMIN_USER}' | base64 --decode && echo
kubectl get secret <secret-name> -n <namespace> -o jsonpath='{.data.MONGODB_DATABASE_ADMIN_PASSWORD}' | base64 --decode && echo

Run a container with a MongoDB client and connect its console output to your terminal. The following command does this, naming the new Pod percona-client:
```
kubectl -n <namespace> run -i --rm --tty percona-client --image=percona/percona-server-mongodb:8.0.26-11 --restart=Never -- bash -il
```
It may take some time to deploy the corresponding Pod.
Now run mongosh tool inside the percona-client command shell using the admin user credentials you obtained from the Secret, and a proper namespace name instead of the <namespace name> placeholder. The command will look different depending on whether sharding is on (the default behavior) or off:
sharding is onsharding is off
mongosh "mongodb://databaseAdmin:databaseAdminPassword@my-cluster-name-mongos.<namespace name>.svc.cluster.local/admin?ssl=false"
mongosh "mongodb+srv://databaseAdmin:databaseAdminPassword@my-cluster-name-rs0.<namespace name>.svc.cluster.local/admin?replicaSet=rs0&ssl=false"

Last update: September 2, 2026
Created: September 2, 2026