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.
We’ve upgraded our feedback system to better capture, track, and act on your feedback. Here’s what you need to know:
|
What problem are you trying to solve? Focus on the what and why of the need you have, not the how you'd like it solved. |
We are working on an edge environment with limited connectivity. So we actually cannot manage it directly. But we want to create some user and theirs database. |
|
What would you like to see happen? Describe the desired outcome or enhancement. |
We should declare a resource for user and database and the operator should create the database and a secret to access it. |
|
Why is this important to you or your team? Explain how the request adds value or solves a business need. |
Actually we deploy our own operator that do the job. So if the new operator have this features we could delete this one and keep only the new mongodb-operator. |
What steps, if any, are you taking today to manage this problem? |
We developed our own operator to manage the creation of database and the creation of user and its secret. |
Hi, my name is Vinicius and I am the PM of the MongoDB Controllers for Kubernetes.
Thank you very much for sharing your feedback and for describing your use case, it’s really helpful for us to understand how you’re using the MongoDB Controllers for Kubernetes, especially in edge environments with limited connectivity. At this time, we don’t plan for the operator to create individual databases directly. Database creation and lifecycle management are part of the data plane, whereas the operator’s focus remains on the control plane, deploying, configuring, and maintaining MongoDB clusters.
That said, user management is supported through the operator. You can find details and examples in our documentation here: Manage Users with the MongoDB Operator
We really appreciate your feedback, use cases like yours help us evaluate potential future enhancements and clarify where our operator should provide value.