# Different image tags available from different registry namespaces

**URL:** <https://forums.percona.com/t/different-image-tags-available-from-different-registry-namespaces/22242>\
**Category:** Percona Operator for MongoDB\
**Created:** [May 22, 2023, 3:55pm UTC](https://forums.percona.com/t/different-image-tags-available-from-different-registry-namespaces/22242 "2023-05-22T15:55:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rdxmbr](https://avatars.discourse-cdn.com/v4/letter/r/c2a13f/32.png) [@rdxmbr](https://forums.percona.com/u/rdxmbr)\
**Post date:** [May 22, 2023, 3:55pm UTC](https://forums.percona.com/t/different-image-tags-available-from-different-registry-namespaces/22242/1 "2023-05-22T15:55:33Z")

</div>

Hello,

I am wondering about that:

```auto
docker pull perconalab/percona-server-mongodb-operator:1.15.0
1.15.0: Pulling from perconalab/percona-server-mongodb-operator
e95f54437d9b: Downloading [=======>] 8.618MB/56.24MB
# ----------- snip -----------

```

but

```auto
# docker pull percona/percona-server-mongodb-operator:1.15.0
Error response from daemon: manifest for percona/percona-server-mongodb-operator:1.15.0 not found: manifest unknown: manifest unknown

```

but

```auto
# docker pull percona/percona-server-mongodb-operator:1.14.0
1.14.0: Pulling from percona/percona-server-mongodb-operator
ba958a445f00: Downloading [===>] 2.739MB/37.85MB
# --------- snip ---------

```

I’ve just recognized that, when I switched from [operator-bundle](https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/main/deploy/bundle.yaml) to the [operator helm chart](https://docs.percona.com/percona-operator-for-mongodb/helm.html).

However, the problem only occurs with deploying the `cr.yaml` with

```auto
spec
  crVersion: 1.15.0

```

> Failed to pull image “percona/percona-server-mongodb-operator:1.15.0”: rpc error: code = NotFound desc = failed to pull and unpack image “[docker.io/percona/percona-server-mongodb-operator:1.15.0](http://docker.io/percona/percona-server-mongodb-operator:1.15.0)”: failed to resolve reference “[docker.io/percona/percona-server-mongodb-operator:1.15.0](http://docker.io/percona/percona-server-mongodb-operator:1.15.0)”: [docker.io/percona/percona-server-mongodb-operator:1.15.0:](http://docker.io/percona/percona-server-mongodb-operator:1.15.0:) not found

---

<div class="post-metadata">

**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\
**Post date:** [May 26, 2023, 7:35am UTC](https://forums.percona.com/t/different-image-tags-available-from-different-registry-namespaces/22242/2 "2023-05-26T07:35:53Z")

</div>

It is a mistake. There should no be 1.15 at all as it is not released yet.  
@Tomislav_Plavcic would appreciate if you can check.

---

<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:** [May 31, 2023, 7:02am UTC](https://forums.percona.com/t/different-image-tags-available-from-different-registry-namespaces/22242/3 "2023-05-31T07:02:13Z")

</div>

Hi @rdxmbr !  
Yes, we might have 1.15.0 in “perconalab” dockerhub repo (which is a testing repo), but 1.15.0 is not released yet so not sure why you put that version in your cr.yaml?  
It simply should not be used by end users.  
Technically whenever we have a lets say 1.14.0 release in “percona” repo, we immediatelly push 1.15.0 to “perconalab” repo because it’s needed for some of our tests.

Kinds regards,  
Tomislav

---

<div class="post-metadata">

**Author:** ![rdxmbr](https://avatars.discourse-cdn.com/v4/letter/r/c2a13f/32.png) [@rdxmbr](https://forums.percona.com/u/rdxmbr)\
**Post date:** [June 26, 2023, 10:36am UTC](https://forums.percona.com/t/different-image-tags-available-from-different-registry-namespaces/22242/4 "2023-06-26T10:36:20Z")

</div>

Hi @Tomislav_Plavcic

sorry, I missed your post.

As I already wrote, it happened

> when I switched from [operator-bundle](https://raw.githubusercontent.com/percona/percona-server-mongodb-operator/main/deploy/bundle.yaml) to the [operator helm chart](https://docs.percona.com/percona-operator-for-mongodb/helm.html).

I expect the helm chart with default values running with the stable release. From the docs [Install with Helm - Percona Operator for MongoDB](https://docs.percona.com/percona-operator-for-mongodb/helm.html#installation) it seems that defining the release version is optional.

Kind regards!