Skip to Main Content

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.

Status Submitted
Categories Atlas
Created by Guest
Created on Nov 21, 2023

Do not require Project Custom Resource for managing other Resources

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.
  • Attach files