v2.14.1

MongoDB Atlas Operator 2.14.1

Improvements and fixes

• fix: Resolved an issue with FlexCluster and DatabaseUser resources when incorrect annotation was set, preventing these resources from being exported correctly by the atlas cli #3342 by @helderjs

Additional Information

• Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator
• Supported Kubernetes versions updated in this release: 1.33 - 1.35
• Supported OpenShift versions updated: 4.21
• See our full compatibility matrix here.

v2.14.0

MongoDB Atlas Operator 2.14.0

Improvements and fixes

• new: Atlas Kubernetes Operator now includes custom resources that are automatically generated based on the OpenAPI Atlas API specification. Refer to the documentation for comprehensive details.
• fix: Resolved an issue where AtlasDeployment resources, when configured with terminationProtectionEnabled: true in the UI, could cause AKO to enter an infinite reconciliation loop. #3334 by @ashortt-mdb
• fix: Resolved an issue where AKO was unable to correctly parse the MongoDB connection URI (mdb URI) required for creating connection secrets. #3223 by @igor-karpukhin
• fix: Resolved an issue where AKO would become stuck while reconciling AtlasDeployment resources due to an error with the ebsVolumeType field. #3334 by @josvazg

Additional Information

• Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator
• Supported Kubernetes versions updated in this release: 1.33 - 1.35
• Supported OpenShift versions updated: 4.21
• See our full compatibility matrix here.

v2.13.2

MongoDB Atlas Operator 2.13.2

Improvements and fixes

• Fixed sorting of deployment regions for the AtlasDeployment resource according to their specified priority, aligning with the Atlas API's requirement for these regions to be received in descending order of priority. https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-creategroupcluster #3166 by @segui-mdb
• Removed the validation requirement for the spec.searchNodes[].instanceSize field within the AtlasDeployment resource. Users can now specify a complete and unrestricted set of search deployment instance types. #3181 by @igor-karpukhin. Resolves #3168

Additional Information

• Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator
• Supported Kubernetes versions updated in this release: 1.33 - 1.35
• Supported OpenShift versions updated: 4.20
• See our full compatibility matrix here.

v2.13.1

MongoDB Atlas Operator 2.13.1

Improvements and fixes

• The Operator no longer enforces the same-instance-size restriction for Analytics nodes. You can now configure Analytics nodes with a different instance size (tier) from Electable, and ReadOnly nodes within an AtlasDeployment resource. #3096 by @igor-karpukhin

Additional Information

• Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator
• Supported Kubernetes versions updated in this release: 1.32 - 1.34
• Supported OpenShift versions updated: 4.20
• See our full compatibility matrix here.

v2.13.0

MongoDB Atlas Operator 2.13.0

Improvements and fixes

• Added support for dynamic indexes configuration in AtlasDeployment Search mappings. See the documentation for more details. #2629 by @s-urbaniak

Additional Information

• Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator
• Supported Kubernetes versions updated in this release: 1.32 - 1.34
• Supported OpenShift versions updated: 4.20
• See our full compatibility matrix here.

v2.12.0

MongoDB Atlas Operator 2.12.0

Improvements and fixes

• Ends serverless cluster support: As announced previously, you can no longer create new Serverless clusters. Existing Serverless cluster specs can still be migrated to Flex specs or deleted. #2926 by @helderjs
• Enables concurrent reconciliation for all resources. Updates are now more performant, as multiple changes are processed simultaneously. #2717 by @s-urbaniak
• Previously resources were not updated in Atlas if the skip annotation was removed. Now if the skip annotation is removed, any pending changes in any resource are synchronised to Atlas immediately. #2839 by @josvazg
• Fix: Some Flex clusters that were created during the transition between Serverless and Flex failed to be updated by the operator. #2926, fixing issue #2890 by @helderjs
• Fix: The skip reconciliation annotation was being ignored for Org Settings and Third Party Integrations. #2903 by @helderjs

Additional Information

• Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator
• Supported Kubernetes versions updated in this release: 1.32 - 1.34
• Supported OpenShift versions updated: 4.20
• See our full compatibility matrix here.

v2.11.1

MongoDB Atlas Operator 2.11.1

Improvements and fixes

• Fix helm charts to include missing fields: Resolved an issue where the fields for overriding the Alert Configuration Severity (in Atlas Project’s Alert Configurations) and Server Management Modes (in Atlas Deployments) were missing when installing the MongoDB Atlas Kubernetes via helm: #2759 by @roothorp.

Additional Information

Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator
Supported Kubernetes versions updated in this release: 1.31 - 1.33
Supported OpenShift versions updated: 4.18
See our full compatibility matrix here.

v2.11.0

MongoDB Atlas Operator 2.11.0

Improvements and fixes

• Manage Atlas Organization Settings via CRD: Adds support for Organization Setting Management directly through the Atlas Kubernetes Operator. This extends the IaC capabilities for more complete, version-controlled management of your Atlas environment. For more information, see Atlas Organization Settings Custom Resource. #2580 & #2621 by @igor-karpukhin
• Override Alert Configuration Severity: Adds support for overriding the severity for Atlas Project’s Alert Configurations, allowing more granular control over alerts. Levels available include CRITICAL, ERROR, WARNING,INFO. #2637 by @gen-sampson
• Configure Server Management Mode: Adds support for configuring the server management mode flag for Atlas Deployments, to be either ATLAS_MANAGED or FIXED_TO_DEDICATED, using a dedicated config server. #2538 by @tvdw-mongodb

Additional Information

Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator
Supported Kubernetes versions updated in this release: 1.31 - 1.33
Supported OpenShift versions updated: 4.18
See our full compatibility matrix here.

v2.10.0

MongoDB Atlas Operator 2.10.0

Improvements and fixes

• Adds support for in-place upgrades from Flex to Dedicated clusters directly through the Atlas Kubernetes Operator. For more information, see Flex to Dedicated migration guide. #2526 by @helderjs
• Updates DEBUG logging level to include detailed differences of resources that the Atlas Kubernetes Operator changes. For more information, see Log Resource Diffs. #2525 by @igor-karpukhin

Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

Supported Kubernetes versions updated in this release: 1.31 - 1.33
Supported OpenShift versions updated: 4.18
See our full compatibility matrix here.

v2.9.1

MongoDB Atlas Operator 2.9.1

Improvements and fixes

• Fixed a bug with missing RBAC for the AKO 2.9.0 on Openshift causing AKO not able to create AtlasThirdPartyIntegration resources in Atlas. #2421 by @josvazg
• Fixed a bug that could stop AKO from syncing a resource to Atlas if an AtlasThirdPartyIntegration was created or modified. #2422 @josvazg
• Fixed a bug that could cause AtlasThirdPartyIntegration to repeatedly update in a loop when importing existing integrations in Atlas. #2425 by @josvazg

Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator

Supported Kubernetes versions updated in this release: 1.30 - 1.32
Supported OpenShift versions updated: 4.18
See our full compatibility matrix here.