Skip to content

MongoDB Enterprise Kubernetes Operator 1.3.0
Compare
Choose a tag to compare
@BenElgar BenElgar released this 25 Oct 17:11
· 228 commits to master since this release
1.3.0
c61d299
This commit was signed with the committer’s verified signature. The key has expired.
BenElgar Ben Elgar
GPG key ID: EB0DF46167A3E0B2
Expired
Learn about vigilant mode.

Important: This release introduces significant changes that may not be compatible with previous deployments or resource configurations. Read https://docs.mongodb.com/kubernetes-operator/stable/tutorial/migrate-to-single-resource/ before installing or upgrading the Kubernetes Operator.

Specification Schema Changes

  • Moves to a one cluster per project configuration. This follows the warnings introduced in a previous version of the operator. The operator now requires each cluster to be contained within a new project.
  • Authentication settings are now contained within the security section of the MongoDB resource specification rather than the project ConfigMap.
  • Replaces the project field with the spec.opsManager.configMapRef.name or spec.cloudManager.configMapRef.name fields.
  • User resources now refer to MongoDB resources rather than project ConfigMaps.
  • No longer requires data.projectName in the project ConfigMap. The name of the project defaults to the name of the MongoDB resource in Kubernetes.

Ops Manager Resource Changes

This release introduces signficant changes to the Ops Manager resource’s architecture. The Ops Manager application database is now managed by the Kubernetes Operator, not by Ops Manager.

Bug Fixes

  • Stops unnecessary recreation of NodePorts.
  • Fixes logging so it’s always in JSON format.
  • Sets USER in the Kubernetes Operator Docker image.
Assets 2
Loading