MongoDB Enterprise Kubernetes Operator 1.7.1

New features

• LDAP : added “spec.security.authentication.agents.automationLdapGroupDN” field to the CRD
• Make agent.auth mandatory if more than one auth mode is specified
• Added the possibility to specify agent startup parameters:
  • “spec.agent.startupOptions” for replica sets/standalone
  • “spec.configSrv.agent.startupOptions”, “spec.mongos.agent.startupOptions”, “spec.shard.agent.startupOptions” for sharded clusters
  • “spec.applicationDatabase.agent.startupOptions” for AppDB

Bug fixes

• MongoDBOpsManager resource:
  • Backing databases with SCRAM-SHA authentication enabled can be of any version if Ops Manager has version 4.4 and above
  • AppDB Monitoring is now correctly configured in Ops Manager when TLS is configured for the AppDB
    The Ops Manager CA configuration property has moved from "spec.applicationDatabase.security.tls.ca" to "spec.security.tls.ca"
• MongoDB resource:
  • Fixed issue where MongoDB 4.4 Replica Sets and Sharded Clusters could not be scaled correctly
  • Fixed an issue in which the operator couldn’t enable agent authentication if only LDAP authentication for the deployment was enabled
  • SCRAM users creation operation and enabling SCRAM authentication in MongoDB resource operation can be done in any order
    Backup automation config is now removed before launching the agent

Known Issues

• ‘spec.applicationDatabase.version” field should not be configured for MongoDBOpsManager resource if AppDB has TLS enabled
  AppDB MongoDB version 4.4+ is not supported
• 1.7.0 release of the Operator made changes to the Deployment configuration which may require to delete the ‘mongodb-enterprise-operator’ Deployment before the upgrade. This is a safe operation as the existing Custom Resources won’t be affected.
• If using TLS certificates signed with a custom certificate authority, the following should be taken into consideration:
  • The “version” of spec.applicationDatabase should not be set (the default version will be used)
  • Ops Manager will have to be configured in “Local Mode”. Every MongoDB version required will need to be copied to Ops Manager in order to be fetched from the database images.