MCK 1.15.0 Release Notes

New Features

• Enterprise Server UBI 9 Slim images: Add support for MongoDB Enterprise Server UBI 9 Slim images for static architecture deployments, and for the Ops Manager Application Database in both architectures improving our security posture. Select the image type operator-wide with the operator.mdbDefaultImageType Helm value (MDB_DEFAULT_IMAGE_TYPE environment variable), or per resource with the mongodb.com/v1.containerImageType annotation on MongoDB, MongoDBMultiCluster, or MongoDBOpsManager (for its Application Database). Supported values are ubi8, ubi9, and ubi9-slim. When no image type is set, existing deployments are unchanged: static architecture deployments use ubi9 and non-static Application Databases use ubi8. An unsupported value falls back to that default, with a warning in the operator log for the Helm value or in the resource status for the annotation. The annotation is ignored, with a status warning, on non-static MongoDB and MongoDBMultiCluster resources.
• MongoDBOpsManager: Added multi-cluster support to the external Application Database feature. spec.externalApplicationDatabaseRef now accepts kind: MongoDBMultiCluster, where the referenced MongoDBMultiCluster must set spec.role: AppDB. Forward and reverse migration between an internal and an external AppDB are supported per member cluster.
• MongoDBSearch: Added spec.clusters[].service.metadata.labels and .annotations to set metadata on the Services the operator creates. shardOverrides[].service overrides them per shard. Operator-managed label keys (app, component, shard, mongodb.com/search-name, mongodb.com/search-namespace) are rejected.

Bug Fixes

• MongoDBOpsManager: Fixed a bug where the Operator could briefly show a false Failed status with the message "The admin-key secret might be corrupted" during an Ops Manager upgrade while the Application Database restarts. The status now remains stable during this transient period.
• MongoDBCommunity: Fixed an issue where the operator could delete a connection string Secret that belongs to another resource. The operator now only removes Secrets it manages and reports a clear error if the configured Secret belongs to something else.
• MongoDB (sharded clusters): Fixed an issue where decreasing spec.shardCount could leave the resource in the Failed phase with cannot have more than 1 MongoDB Cluster per project, because the removed shard was not fully removed from Ops Manager.
• MongoDBOpsManager: Fixed an issue where changing the Application Database password could leave Ops Manager in the Failed phase with The admin-key secret might be corrupted, because the new password was never applied to the Application Database.
• MongoDBSearch: Updated the default metrics forwarder image to otel/opentelemetry-collector-contrib:0.163.2 and pinned the default managed load balancer image to envoyproxy/envoy:v1.37.11 to address known CVEs. If you override search.metricsForwarderImage, use OpenTelemetry Collector Contrib 0.157.0 or later.
• MongoDBSearch: The Envoy and metrics forwarder containers now follow the registry.pullPolicy Helm setting, like the mongot container.
• MongoDB, MongoDBCommunity, MongoDBOpsManager: Fixed a bug where volumeAttributesClassName set in a volumeClaimTemplates entry of a statefulSet override was silently dropped, so the resulting PersistentVolumeClaims had no VolumeAttributesClass. A change to this field on an existing StatefulSet is now also detected as a change to an immutable field.
• MongoDB, MongoDBMultiCluster, MongoDBUser: Fixed a bug where the operator ignored the configured Vault database secret path and read database secrets from the operator secret path instead. Database secret data and metadata now use the configured database path.
• MongoDBMultiCluster: Fixed a bug where hostname override ConfigMaps used the position of a cluster in spec.clusterSpecList instead of its stable mapping index. Reordering the list could give pods hostnames from another cluster.
• Bump Go to 2.6.10 to avoid emudhra incident.

Other Changes

• MongoDB: The Standalone deployment architecture is deprecated and will not be supported in the next major version. Migrate to a one member ReplicaSet and copy the data with mongodump and mongorestore.