MongoDB Enterprise Kubernetes Operator 1.27.0
New Features
-
MongoDB: Added Support for enabling LogRotation for MongoDB processes, MonitoringAgent and BackupAgent. More can be found in the following documentation.
spec.agent.mongod.logRotationto configure the mongoDB processesspec.agent.mongod.auditLogRotationto configure the mongoDB processes audit logsspec.agent.backupAgent.logRotationto configure the backup agentspec.agent.monitoringAgent.logRotationto configure the backup agentspec.agent.readinessProbe.environmentVariablesto configure the environment variables the readinessProbe runs with.
That also applies to settings related to the logRotation,
the supported environment settings can be found here.- the same applies for AppDB:
- you can configure AppDB via
spec.applicationDatabase.agent.mongod.logRotation
- you can configure AppDB via
- Please Note: For shardedCluster we only support configuring logRotation under
spec.Agent
and not per process type (mongos, configsrv etc.)
-
Opsmanager: Added support for replacing the logback.xml which configures general logging settings like logRotation
spec.logging.LogBackAccessRefpoints at a ConfigMap/key with the logback access configuration file to mount on the Pod- the key of the configmap has to be
logback-access.xml
- the key of the configmap has to be
spec.logging.LogBackRefpoints at a ConfigMap/key with the logback access configuration file to mount on the Pod- the key of the configmap has to be
logback.xml
- the key of the configmap has to be
-
OpsManager: Added support for configuring
votes,priorityandtagsfor application database nodes in the multi-cluster topology under thespec.applicationDatabase.clusterSpecList[i].memberConfigfield.
Deprecations
- AppDB: logRotate for appdb has been deprecated in favor for the new field
- this
spec.applicationDatabase.agent.logRotationhas been deprecated forspec.applicationDatabase.agent.mongod.logRotation
- this
Bug Fixes
-
Agent launcher: under some resync scenarios we can have corrupted journal data in
/journal.
The agent now makes sure that there are not conflicting journal data and prioritizes the data from/data/journal.- To deactivate this behaviour set the environment variable in the operator
MDB_CLEAN_JOURNAL
to any other value than 1.
- To deactivate this behaviour set the environment variable in the operator
-
MongoDB, AppDB, MongoDBMulti: make sure to use external domains in the connectionString created if configured.
-
MongoDB: Removed panic response when configuring shorter horizon config compared to number of members. The operator now signals a
descriptive error in the status of the MongoDB resource. -
MongoDB: Fixed a bug where creating a resource in a new project named as a prefix of another project would fail, preventing the
MongoDBresource to be created.