On this page
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 Key in an Organization and configure the API Access List.Important
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 Key for a Project and configure the API Access List.Important
You must assign the API key the Project Owner project role.
To learn more, see Configure Access to Atlas.
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:
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
spec.scopes parameter in the
custom resource restricts the clusters that create the database
To connect to the Atlas Administration API, Atlas Kubernetes Operator reads the organization ID and API keys from one of the following locations:
spec.connectionSecretRef.name(if specified in the
globalAtlas Kubernetes Operator secret
spec.connectionSecretRef.nameis not specified).
To create or update resources in Atlas, Atlas Kubernetes Operator uses the connection information to make API calls to Atlas.
If any errors occur during the reconciliation,
updates to reflect the error.
- lastTransitionTime: "2021-03-15T14:26:44Z" message: 'POST https://cloud.mongodb.com/api/atlas/v1.0/groups/604a47de73cd8cag77239021/accessList: 400 (request "INVALID_IP_ADDRESS_OR_CIDR_NOTATION") The address 192.0.2.1dfdfd5 must be in valid IP address or CIDR notation.' reason: ProjectIPAccessListNotCreatedInAtlas status: "False" type: IPAccessListReady