Use docker images from a custom registry

Using images from a private Docker registry may be useful in different situations: it may be related to storing images inside of a company, for privacy and security reasons, etc. In such cases, Percona Server for MongoDB Operator allows to use a custom registry, and the following instruction illustrates how this can be done by the example of the Operator deployed in the OpenShift environment.

  1. First of all login to the OpenShift and create project.

     $ oc login
     Authentication required for (openshift)
     Username: admin
     Login successful.
     $ oc new-project psmdb
     Now using project "psmdb" on server "".
  2. There are two things you will need to configure your custom registry access:

    • the token for your user
    • your registry IP address.

    The token can be find out with the following command:

     $ oc whoami -t 

    And the following one tells you the registry IP address:

     $ kubectl get services/docker-registry -n default
     NAME              TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
     docker-registry   ClusterIP   <none>        5000/TCP   1d
  3. Now you can use the obtained token and address to login to the registry:

     $ docker login -u admin -p ADO8CqCDappWR4hxjfDqwijEHei31yXAvWg61Jg210s
     Login Succeeded
  4. Pull the needed image by its SHA digest:

     $ docker pull
     Trying to pull repository ...
     sha256:69c935ac93d448db76f257965470367683202f725f50d6054eae1c3d2e731b9a: Pulling from
     Digest: sha256:69c935ac93d448db76f257965470367683202f725f50d6054eae1c3d2e731b9a
     Status: Image is up to date for
  5. The following way is used to push an image to the custom registry (into the OpenShift psmdb project):

     $ docker tag \ \
     $ docker push
  6. Check the image in the OpenShift registry with the following command:

     $ oc get is
     NAME                              DOCKER REPO                                                             TAGS             UPDATED
     percona-server-mongodb-operator   docker-registry.default.svc:5000/psmdb/percona-server-mongodb-operator  0.2.1-mongod3.6  2 hours ago
  7. When the custom registry image is Ok, put a Docker Repo + Tag string (it should look like docker-registry.default.svc:5000/psmdb/percona-server-mongodb-operator:0.2.1-mongod3.6) into the image: option in deploy/operator.yaml configuration file.

    Please note it is possible to specify imagePullSecrets option for all images, if the registry requires authentication.

  8. Repeat steps 3-5 for other images, and update corresponding options in the deploy/cr.yaml file.

  9. Now follow the standard Percona Server for MongoDB Operator installation instruction.

Percona certified images

Following table presents Percona’s certified images to be used with the Percona Server for MongoDB Operator:


Image Digest
percona/percona-server-mongodb-operator:0.3.0 69d2018790ed14de1a79bef1fd7afc5fb91b57374f1e4ca33e5f48996646bb3e
percona/percona-server-mongodb-operator:0.3.0-mongod3.6.10 a02a10c9e0bc36fac2b1a7e1215832c5816abfbbe0018fca61d133835140b4e8
percona/percona-server-mongodb-operator:0.3.0-mongod4.0.6 0849fee6073e85414ca36d4f394046342d623292f03e9d3afd5bd5b02e6df812
percona/percona-server-mongodb-operator:0.3.0-backup 5a32ddf1194d862b5f6f3826fa85cc4f3c367ccd8e69e501f27b6bf94f7e3917
perconalab/pmm-client:1.17.1 f762cda2eda9ef17bfd1242ede70ee72595611511d8d0c5c46931ecbc968e9af