MongoDB Atlas Operator 2.5.0

New features

Support for local credentials for custom resources, allowing specific custom resources to be managed using specific Atlas Admin API credentials: CLOUDP-266544 #1782 by @josvazg
AtlasDeployment can now be used as an independent resource, meaning you can manage Atlas Deployments without also managing the Project using the Atlas Kubernetes Operator CLOUDP-267957 #1773 by @helderjs
AtlasDatabaseUser can now be used as an independent resource, meaning you can manage Atlas Database Users without also managing the Project using the Atlas Kubernetes Operator CLOUDP-266544 #1769 by @helderjs
New "basic deployment" and "advanced deployment" helm templates that allow provisioning of Atlas Projects, Deployments, and Database Users for two scenarios (basic and advanced) CLOUDP-206785 #348 by @igor-karpukhin

Fixed the case when changing the Instance Size was ignored for a shared cluster CLOUDP-278494 #1867 by @helderjs
Resolved Operator panics when changing a deployment to/from serverless CLOUDP-278492 #1869 by @helderjs
Cleanup of orphan connection strings after a Database User was deleted CLOUDP-277876 #1856 by @josvazg
Fixed the case when an AtlasTeam resource that is not managed by the Atlas Operator (not assigned to any AtlasProject resource) was wrongly deleted CLOUDP-273419 #1829 by @helderjs
Remove custom ResourceWatcher in favor of controller-runtime field indexers. The legacy internal custom ResourceWatcher had bugs and its usage was error prone which could lead to lost data and data integrity issues with resources managed by Atlas Operator: CLOUDP-244158 by @s-urbaniak

Images can be found in: https://quay.io/mongodb/mongodb-atlas-kubernetes-operator
Supported Kubernetes versions updated in this release: 1.28-1.30
Supported OpenShift versions updated: 4.16
Full Changelog: v2.4.1...v2.5.0