Docs Menu
Docs Home
/ /
MongoDB Atlas Kubernetes Operator

Production Notes

On this page

  • Atlas Account
  • API Keys
  • Namespaces
  • AWS Security Groups
  • Deprecated Configuration Parameters
  • Cluster Creation
  • Connection Strings
  • Connection Information
  • Supported Deployment Flags

You can access the Atlas Kubernetes Operator project on GitHub:


Before you deploy Atlas Kubernetes Operator, you must create an Atlas account. To learn more, see Register a new Atlas Account.

You need the following public API key, private API key, and the organization ID information to configure Atlas Kubernetes Operator access to Atlas.

  • If you want Atlas Kubernetes Operator to create a new Atlas project, Create an API (Application Programming Interface) Key in an Organization. If your organization requires an IP access list for the Atlas Administration API, you must also configure the API access list.


    You must assign the API key the Organization Project Creator organization role or higher.

  • If you want to work with an existing Atlas project, Create an API (Application Programming Interface) Key for a Project. If your organization requires an IP access list for the Atlas Administration API, you must also configure the API access list.


    You must assign the API key the Project Owner project role.

To learn more, see Configure Access to Atlas.

You can deploy Atlas Kubernetes Operator to watch all the namespaces in the Kubernetes cluster, or only its namespace.

You must configure VPC peering for your project before you can add an AWS security group to an access list. You can't set AWS security groups as temporary access list entries.

The following parameters are deprecated in the Atlas API and Atlas Kubernetes Operator doesn't support them:

  • replicationSpec

  • replicationFactor

Creating a new cluster can take up to 10 minutes.

You can't use a connection URL directly. Atlas clusters require authentication. You must create at least one AtlasDatabaseUser Custom Resource before the application in your Kubernetes cluster can connect to the Atlas cluster. Atlas Kubernetes Operator creates a special secret for each cluster and database user combination in the project. The application in your Kubernetes cluster can use this secret to connect to the Atlas cluster. The spec.scopes parameter in the AtlasDatabaseUser custom resource restricts the clusters that create the database user.

To connect to the Atlas Administration API, Atlas Kubernetes Operator reads the organization ID and API keys from one of the following locations:

  • (if specified in the AtlasProject Custom Resource).


    By default, Atlas Kubernetes Operator keeps connection secrets in the same namespace as the AtlasProject Custom Resource. To store secrets in another namespace, specify the spec.connectionSecretRef.namespace parameter.

  • global Atlas Kubernetes Operator secret <operator-deployment-name>-api-key (if is not specified).

To create or update resources in Atlas, Atlas Kubernetes Operator uses the connection information to make API calls to Atlas.


Sometimes Atlas Kubernetes Operator makes multiple API calls in Atlas during the reconciliation of a custom resource. For example, AtlasProject has an IP Access List configuration for calling the matching API.

If any errors occur during the reconciliation, status.conditions updates to reflect the error.


- lastTransitionTime: "2021-03-15T14:26:44Z"
message: 'POST
400 (request "INVALID_IP_ADDRESS_OR_CIDR_NOTATION") The address
must be in valid IP address or CIDR notation.'
reason: ProjectIPAccessListNotCreatedInAtlas
status: "False"
type: IPAccessListReady

When you deploy. Atlas Kubernetes Operator using kubectl, you can add the following flags to customize your configuration:

Default Value
Atlas URL domain name, that terminates in a slash.
Address that the metric endpoint binds to.
Address that the probe endpoint binds to.
Name of the secret that contains your Atlas API keys. Atlas Kubernetes Operator uses this parameter if your AtlasProject configuration doesn't contain an API key reference.
<deployment_name>-api-key, where <deployment-name> is the name of your Atlas Kubernetes Operator deployment.
Flag that indicates whether to enable leader election for controller manager. Leader election ensures that only one controller manager is active at a time.

Importance or urgency level of log entries. You can specify one of the following levels:

  • debug

  • info

  • warn

  • error

  • dpanic

  • panic

  • fatal


Format for log records. You can specify one of the following formats:

  • json

  • console



The following command sets up an Atlas Kubernetes Operator 1.8.2 deployment with the metrics endpoint on port :8084, using a log level of error:

kubectl apply --metrics-bind-address :8084 \
--log-level error \