Document decision for MongoDB #111
Conversation
|
|
||
| Proposal 2: Use MongoDB Enterprise Operator:: | ||
| MongoDB Enterprise Operator can be used to manage MongoDB instances on Kubernetes. | ||
| The licensing allows to use it as a SaaS according to their docs. |
There was a problem hiding this comment.
Since the decision basically hinges on this statement, a link (and potentially a quote here) to the mentioned docs should be included.
There was a problem hiding this comment.
Hmmm... I can't actually find the mentioning of the SaaS again.
However, I since learned we've been in contact with MongoDB already and even have a concrete quote. I adjust the wording here.
| MongoDB Enterprise Operator can be used to manage MongoDB instances on Kubernetes. | ||
| The licensing allows to use it as a SaaS according to their docs. | ||
| There's a https://github.com/mongodb/helm-charts/tree/main/charts/enterprise-operator[helm chart] to deploy it. | ||
| It does need an https://www.mongodb.com/pricing[enterprise license] though. |
There was a problem hiding this comment.
How does this work? Is this enforced somehow? Do we need to distribute MongoDB license information to all customer clusters?
There was a problem hiding this comment.
Yes the operator needs a license key. Not sure if the operator needs to have an outbound connection to a licensing server though.
Also, as far as I know the first business case we have for MongoDB is for Exoscale only, so it would only be deployed for Exoscale in the beginning.
| Use MongoDB Enterprise Operator. | ||
|
|
||
| This is the only viable option to run a MongoDB SaaS on K8s. | ||
| There's no helm based deployment for MongoDB Enterprise Edition. |
There was a problem hiding this comment.
how would we need to implement it?
There was a problem hiding this comment.
I've added a bit more context.
|
We need to involve more stakeholders in this decision as I feel we should not be the only ones to decide. The questions that arise here are more for sales and management.
|
Yes, we do need all the bells and whistles that come with MongoDB as this is what is asked for by the customers from Exoscale. We are proceeding with the cooperation with them and this is a much needed service. |
Co-authored-by: lieneluksika <[email protected]>
Co-authored-by: lieneluksika <[email protected]>
Co-authored-by: lieneluksika <[email protected]>
Co-authored-by: lieneluksika <[email protected]>
Summary
Checklist
change,decision,requirement/quality,requirement/functional,dependencyas they show up in the changelog