Andre
My feedback
2 results found
-
5 votes
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.
Andre
supported this idea
·
An error occurred while saving the comment -
14 votes
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.