Atlas Kubernetes Operator Changelog

On this page

Note

You can find the full list of Atlas Kubernetes Operator releases here.

Atlas Kubernetes Operator 0.8.0

Upgrades the Controller Runtime to v0.11.0.
Upgrades Go to 1.17.
When you install a cluster using Helm Charts, Helm doesn't exit until the cluster is ready if you set postInstallHook.enabled to true.
Atlas Kubernetes Operator watches secrets only with the label atlas.mongodb.com/type=credentials to avoid watching unnecessary secrets.
Supports the mongodb.com/atlas-reconciliation-policy=skip annotation for configuring Atlas Kubernetes Operator to skip reconciliations on specific resources.
Supports X.509 authentication.

Adds the spec.advancedClusterSpec parameter to the AtlasCluster Custom Resource. The AtlasCluster custom resource now has two main configuration options. You must specify either spec.clusterSpec or spec.advancedClusterSpec. The spec.clusterSpec parameter uses the Atlas Cluster API Resource. The spec.advancedClusterSpec parameter uses the Atlas Advanced Cluster API Resource.
Note
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.

You can find the images in the following location:

This Atlas Kubernetes Operator trial release lets you manage Atlas projects, clusters, and database users with Kubernetes specifications.

Introduces Global and per project Atlas authentication modes. To learn more, see Configure Access to Atlas.
Supports installing Atlas Kubernetes Operator clusterwide (all the namespaces in the Kubernetes cluster) or to its own namespace. To learn more, see Quick Start.
Introduces the AtlasProject Custom Resource. Use this resource to create Atlas projects and configure their IP access lists.
Introduces the AtlasCluster Custom Resource. Use this resource to create clusters in an Atlas project.
Introduces the AtlasDatabaseUser Custom Resource for creating database users in an Atlas project.
Allows you to create or update secrets for each database user and cluster. Applications can use these secrets in Kubernetes to connect to Atlas clusters.