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.