Arthur
My feedback
2 results found
-
7 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.
Arthur
supported this idea
·
-
8 votes
This is something we're considering for the future.
But the biggest problem we need to solve is that it's incredibly easy to create/delete/update databases within a deployment via many other interfaces. But if this happens, the Operator's source of truth (the custom resources) won't contain the changes, and the Operator would overwrite the changes using it's source of truth.
An error occurred while saving the comment Arthur
supported this idea
·
We had begun implementing a full IaC-based solution leveraging the MongoDB Atlas Operator. However, we've currently paused this effort, as it would require us to decouple the "Cluster and Settings Provisioning" from "Database Users and Roles Management" across separate tools—or worse, revert to managing certain aspects via the UI.
Our goal is to maintain a single source of truth where all configurations, including access controls, can be managed declaratively through IaC and GitOps practices.