Name and Version
mongodb-sharded-6.6.7
What architecture are you using?
amd64
What steps will reproduce the bug?
I deployed mongodb on the GKE cluster. It has been running well but yesterday all pods in the statefulset went down with an error Unrecognized option: storage.journal.enabled.
I deployed via helm.
Helm repository https://charts.bitnami.com/bitnami
What is the expected behavior?
No response
What do you see instead?
05:54:06.20 INFO ==> Setting node as primary
mongodb 05:54:06.23
mongodb 05:54:06.24 Welcome to the Bitnami mongodb-sharded container
mongodb 05:54:06.24 Subscribe to project updates by watching https://github.com/bitnami/containers
mongodb 05:54:06.24 Submit issues and feature requests at https://github.com/bitnami/containers/issues
mongodb 05:54:06.24
mongodb 05:54:06.24 INFO ==> ** Starting MongoDB Sharded setup **
mongodb 05:54:06.27 INFO ==> Validating settings in MONGODB_* env vars...
mongodb 05:54:06.33 INFO ==> Initializing MongoDB Sharded...
mongodb 05:54:06.37 INFO ==> Writing keyfile for replica set authentication...
mongodb 05:54:06.39 INFO ==> Enabling authentication...
mongodb 05:54:06.39 INFO ==> Deploying MongoDB Sharded with persisted data...
mongodb 05:54:06.43 INFO ==> ** MongoDB Sharded setup finished! **
mongodb 05:54:06.47 INFO ==> ** Starting MongoDB **
Unrecognized option: storage.journal.enabled
try '/opt/bitnami/mongodb/bin/mongod --help' for more information
Additional information
No response
Name and Version
mongodb-sharded-6.6.7
What architecture are you using?
amd64
What steps will reproduce the bug?
I deployed mongodb on the GKE cluster. It has been running well but yesterday all pods in the statefulset went down with an error Unrecognized option: storage.journal.enabled.
I deployed via helm.
Helm repository https://charts.bitnami.com/bitnami
What is the expected behavior?
No response
What do you see instead?
Additional information
No response