[s390x] mongodb installation fails with missing image

[witekwww]

Collection version

26.0.1

Environment information

cli:13.2.0
running on s390x architecture

What happened?

Deployment of MongoDB operator (Deployment mongodb-kubernetes-operator) fails during image pull with following error: Failed to pull image "quay.io/mongodb/mongodb-kubernetes-operator@sha256:4e1e6f82d33211ffd164a28d811b106d02546a1ce84c95625404f30a80a0c2d1": rpc error: code = Unknown desc = choosing image instance: no image found in manifest list for architecture s390x, variant "", OS linux This is reproducible with both january 2025 and also december 2024 catalogs in s390x variant.

Relevant log output

Pulling image "quay.io/mongodb/mongodb-kubernetes-operator@sha256:4e1e6f82d33211ffd164a28d811b106d02546a1ce84c95625404f30a80a0c2d1"

Failed to pull image "quay.io/mongodb/mongodb-kubernetes-operator@sha256:4e1e6f82d33211ffd164a28d811b106d02546a1ce84c95625404f30a80a0c2d1": rpc error: code = Unknown desc = choosing image instance: no image found in manifest list for architecture s390x, variant "", OS linux

[durera]

MongoDb is not supported on s390x architecture, our s390x support only includes use with external mongodb. For this reason, the MAS CLI should not present the option to install the mongodb community operator on an s390x cluster when using the CLI itself, but when using the ansible roles natively we don't have that same level of control/guardrails in place.

https://www.ibm.com/docs/en/masv-and-l/cd?topic=new-in-fix-packs

If there's additional documentation you were referencing where this limitation was not clearly stated I'm happy to make updates to that, just let me know where you were looking.