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

MongoDB Enterprise Kubernetes Operator 0.5

Release Notes

• Database image downloads Automation Agent from OpsManager/Cloud Manager during start up
• Bug fix: Fixed Ops Manager/Cloud Manager errors for duplicated project names

MongoDB Enterprise Kubernetes Operator 0.4

Release Notes

• For Replica Set or Sharded Cluster with configured backup, the Operator can now properly orchestrate resource removal and shutdown backup process.
• Improved Persistent Volume support:
  • It is now possible to mount mongodb data, the mongodb journal and all logs into different volumes. Configure podSpec.persistence.multiple to enable this behaviour.
    Define podSpec.persistence.single to mount all there directories into a single volume. This is the default behavior.
  • A new parameter, labelSelector, defines labels for a selector which controls which volumes are mounted.
  • A default StorageClass will be used if storageClass is not defined in the persistence configuration. Most Kubernetes deployments support dynamic volume provisioning, so volumes should be available by default without needing to configure this field.

MongoDB Enterprise Kubernetes Operator 0.3

Release Notes

• The Operator will not create the CustomResourceDefinition objects any more, they need to be created manually by the administrator. A new yaml file is provided (crds.yaml) that can be applied to create/configure these objects.
• ClusterRoles are not required any more. We have changed the way the Operator watches resources. Until the last release, the Operator would watch for any resource on any Namespace. With 0.3, the operator will watch for resources in the same Namespace that it was created in. To support multiple namespaces, multiple Operators can be installed. This allows isolation of MongoDB deployments.
• We have made permissions changes to how PersistentVolumes are mounted.
• Added configuration to operator to not create SecurityContexts for Pods. This solves an issue with OpenShift which disallows this setting when SecurityContextContraints are in place. If using Helm, the variable managedSecurityContext set to true will tell the operator to not create SecurityContexts for Pods, satisfying the OpenShift requirement.
• A combination of projectName and orgId is now used to configure Ops Manager or Cloud Manager. If a project with this projectName does not exist, it will be created by the Operator.

Known Issues

• In a MongoDB deployment with no PersistentVolume configured, disk metrics will not show up in Ops Manager or Cloud Manager Deployments view.

MongoDB Enterprise Kubernetes Operator 0.2

• WiredTiger Cache Size attribute is now set by the operator.

The WiredTiger Cache Size for individual mongods is now set by the operator, considering the memory limits of the mongod container. The formula used to calculate this attribute can be found in this this document.