MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
Status Under Consideration
Categories Atlas
Created by Guest
Created on Nov 20, 2023

RELATED FEEDBACK

Use kubernetes Atlas operator to create and manage only users

We are already managing the Atlas project using terraform and do not want to have two separate tools managing the same resource. We would still like to generate atlas users automatically through the operator. If there was a method of just providing the project ID as a string like we are able to in the terraform resource definition, this would not be a problem.
  • ADMIN RESPONSE
    Aug 1, 2025
    We're planning an investigation into this in Q2 (May-July for us). It's something more than one customer has asked for and allowing an Atlas ID to be used rather than a reference for another K8s resource feels like a reasonable approach. No commitments for now till we've investigated in a little more detail.
  • Attach files
  • Guest
    Nov 21, 2023
    We would like to adopt the Atlas Operator without managing our entire Atlas Project in Kubernetes, or we would like to manage the Project elsewhere, maybe in another namespace, in another k8s cluster or in Terraform. It does not make sense that the `AtlasDatabaseUser` requires a `AtlasProject` resource to exist. We want to manage users separately from the Project as those can be owned by different users in our system. Also the API and Terraform resources do not have this requirement so it breaks convention when the Atlas Operator has this unique requirement https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/database_user To work around this we would have to code our own Operator using the MongoDB API/SDKs or perhaps use Crossplane. We would prefer to use an officially supported operator by MongoDB Atlas.
    Reply