MongoDB Enterprise Kubernetes Operator 0.6

Release Notes

• Codebase was refactored to use controller-runtime library. This fixed some problems when Operator could leave resources in inconsistent state and introduced proper reconciliation process.
  • Important: as the removal process was refactored to use finalizer headers it's important to delete mongodb resources before deleting Operator/namespace otherwise the deletion operation can get stuck. More details in the docs
• New status field for all MongoDB Kubernetes resources
• Operator can be configured to watch any single namespace or all namespaces in a cluster (requires cluster role)
• Database logging has been improved: new configuration property logLevel (INFO by default) was added. Automation Agent and mongodb logs are merged in to a single log stream.
• New configuration Operator timeouts was added. It defines waiting time for database pods start while updating MongoDB Kubernetes resources
• Bug fix: Fixed failure detection for mongos