v0.8.0

MongoDB Atlas Operator v0.8.0

• The Atlas Operator is now in Beta
• Deploying Advanced Atlas Clusters is now supported
• x.509 User Authentication is now supported
• Warning: This release contains breaking changes to the AtlasCluster Resource. See below for details on how to update to the new format. This also applies to the "atlas" section of the atlas-cluster Helm chart.

Atlas Operator

• Changes
  • When installing a cluster using the helm chart, helm will not exit until the cluster is ready if postInstallHook.enabled is set to true.
  • The operator now only watches secrets with the label atlas.mongodb.com/type=credentials to avoid watching unnecessary secrets.
  • It is possible to configure the Operator to skip reconciliations on specific resources by adding the annotation mongodb.com/atlas-reconciliation-policy=skip.
  • Upgrade Controller Runtime to v0.11.0
  • Upgraded to Go 1.17
• Bug fixes
  • Fixed an issue where errors would be logged upon resource deletion.

AtlasProject Resource

• Changes
  • The AtlasProject will not be marked as ready until the Project IP Access List is successfully created.
  • Enable User Authentication using X.509 Certificates

AtlasCluster Resource

• Changes
  • The AtlasCluster now has two main configuration options. You must specify exactly one of
    • spec.clusterSpec or spec.advancedClusterSpec. clusterSpec uses the regular Atlas Cluster API while advancedClusterSpec uses the Atlas Advanced Cluster API
    • Note: in order to migrate an existing resource to use the spec.clusterSpec structure, you must move all fields currently under spec.* to spec.clusterSpec.* with the exception of spec.projectRef

The images can be found in:

https://quay.io/repository/mongodb/mongodb-atlas-operator

v0.7.0

Changes:

• Add private endpoint for AWS and Azure (#355, #365, #367)
• Adding private connection string counterparts. (#344)
• Use finalizers for project deletion (#346)
• Add cluster termination to cleaner (#324)

v0.6.1

Fixes:

• Remove required namespace field from CRD

v0.6.0

Changes:

• Support global secret configuration (#222)
• Remove dots from connection secret fields (#241)
• Reference project from another namespace (#254)
• Do not try to delete non-existing Atlas projects (#240)
• Add annotations to avoid removing resources from Atlas (#213)
• Improve DB user cleanup (#283)
• Pass git version to the binary on build (#195)
• Remove kube-proxy from deployment (#249)

v0.5.0

Changes

• Support for AtlasDatabaseUser Custom Resource
• Atlas cluster connection Secrets are created on updates to AtlasCluster, AtlasDatabaseUser resources
• Deployment configuration improvements: using non-default ServiceAccount, common labels for all deployment configs
• Decreased reconciliation syncPeriod to 3 hours

Bug Fixes

• Fixed an issue with AtlasCluster replicationSpecs configuration

v0.4.0

Changes

• Support for OLM bundles generation
• Support namespace and clusterwide deployment modes
• Support for AtlasCluster replicationSpecs configuration

Bug Fixes

• Fixes an issues with Operator Connection Secret name format

v0.3.0

Changes

• Support for IP Access List in AtlasProject
• Support the Operator-level Connection Secret
• Handling deletion of the AtlasProject
• Connection Secret for AtlasProject is watched by the Operator
• Handling AtlasCluster pause/unpause

v0.2.0

Bug Fixes

• Fixes an issue with AtlasCluster removal
• Adds Operator configuration --atlas-domain that allows configuring the Atlas server to be used

v0.1.0

Initial release that includes basic support for AtlasProject and AtlasCluster resources