Hi,
I think I now understand why altering our kubernetes mongodb setup to not point at a Bitnami image - bitnami/mongodb-exporter:0.32.0 didn’t work, even though it can be found in the Percona repo.
As it’s not in the certified image list for this setup
curl https://check.percona.com/versions/v1/psmdb-operator/1.12.0/5.0.7-6 | jq -r ‘.versions.matrix’
It can’t be downloaded and the pod is stuck in ImagePullBackoff
My question, can it be added to the image list, and if not, what do you suggest as an alternative.
Kind regards,
Mike
Hi, can you explain exactly what is your setup? are you using percona mongodb operator? it has built-in pmm client which includes the mongodb exporter.
If you look carefully you can see the exact version of the operator in use in the curl expression above, it being version 1.12.0. While these days I use Everest and PMM, back then the option was taken to not do so, and the bitnami image was chosen instead, which is what has lead to this situation. I know the image I require exists in the Percona repo, because its downloadable using Docker. But altering the setup to point to Percona doesn’t work either, and it would appear from the version check that it’s not a referenced image. This is currently only effecting one of the three instances, but as it stands we would lose the cluster with a general restart. I’m just looking for a simple and straightforward method of picking up an existing image, as a stopgap before a controlled rebuild of the complete cluster. It seemed to me that adding it to the allowed images might be a simple solution, not just for me but for anyone else who needed to use an image they can no longer access without paying vast sums. Suggestions welcome.