When setting a custom registry url the imageType is ignored

[LinzerToertchen]

When setting a custom registry url the imageType is ignored.

What did you do to encounter the bug?

Deploy the operator with a custom community.mongodb.repo value:

community:
  mongodb:
    repo: registry.example.com/quay.io/mongodb

What did you expect?

I expect the mongodb pods to use the image registry.example.com/quay.io/mongodb/mongodb-community-server:8.2.3-ubi8.

What happened instead?

Due to the logic in controllers/replica_set_controller.go the resulting image tag is registry.example.com/quay.io/mongodb/mongodb-community-server:8.2.3, without the imageType appended. When using a simple pull cache, this fails, because all images are pushed with the variant appended to the tag.

Operator Information

• Operator Version: 1.6.1
• MongoDB Image used: 8.2.3

[Archimonde666]

Encoutering exact same issue here

[qkauffmaASU]

Hitting the same problem, had to set include the imageType in the version of the mongodbcommunity.mongodbcommunity.mongodb.com object

Still showing on the latest branch: controllers/replica_set_controller.go

[abenetton]

Same issue here

[OlliMartin]

Observing the same in 1.6.0, 1.6.1 and 1.7.0.