You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 2nd step encountered an error, complaining about not finding the image. The second step is: kubectl apply -f config/samples/mongodb.com_v1_mongodbcommunity_cr.yaml --namespace <my-namespace>
Additional context
In the mentioned yaml file, the spec section sets the version of mongodb-community-server to "6.0.5" (spec.version = "6.0.5").
Note: In the helm values of 'community-operator-0.11.0' (achieved by helm show values mongodb/community-operator --version 0.11.0 > community-operator-0.11.0_values ), the resource.version is also set to '4.4.0', while there is no such tag on Dockerhub. Changing this tag to '4.4.0-ubuntu2004' resolved the issue in my case.
The text was updated successfully, but these errors were encountered:
So, where the registry of the default images configured?
Also, what is the default image for "type: ReplicaSet" in the mongodb.com_v1_mongodbcommunity_cr yaml file (config/samples/mongodb.com_v1_mongodbcommunity_cr.yaml) ? Is it mongodb-community-server or mongo?
Similarly, What is the default image for "resource: mongodb-replica-set" in the community-operator-0.11.0_values.yaml file from the Community Operator Helm chart?
And, where are the registries for these images specified?
It seems that the default image in both files is "mongodb-community-server".
However, in the values file of the Community Operator Helm chart, there is a section that points to docker.io as the registry for mongodb-community-server:
What did you do to encounter the bug?
Deploying 'mongodb-community-server' Replicaset encounters an error.
Steps to reproduce the behavior:
kubectl apply -f config/samples/mongodb.com_v1_mongodbcommunity_cr.yaml --namespace <my-namespace>
Additional context
In the mentioned yaml file, the spec section sets the version of mongodb-community-server to "6.0.5" (spec.version = "6.0.5").
While MongoDB official image has this tag, there is no such tag on dockerhub for mongodb-community-server image.
In my case, I used 6.0.5-ubuntu2204 to resolve the issue
Note: In the helm values of 'community-operator-0.11.0' (achieved by
helm show values mongodb/community-operator --version 0.11.0 > community-operator-0.11.0_values
), the resource.version is also set to '4.4.0', while there is no such tag on Dockerhub. Changing this tag to '4.4.0-ubuntu2004' resolved the issue in my case.The text was updated successfully, but these errors were encountered: