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