I'm looking for the best way to set up a single MongoDB instance without the added complexity of managing a MongoDB operator. My team oversees numerous Kubernetes clusters and we handle multiple users, so installing an operator just for one instance seems like overkill. What are my alternatives?
To clarify, as part of my role in the platform team, we automate our deployment processes extensively and manage everything from building components to testing and rolling them out. This whole process is tedious and requires significant resources, especially when addressing security vulnerabilities or changes. I want to know if there's a lighter approach to deploying a single MongoDB instance that doesn't involve the overhead of an operator.
1 Answer
It might actually be easier to run a stateful set for a single MongoDB instance instead of dealing with the complexities of an operator. If you don't need extra features like high availability or backups, this could save you a lot of hassle. Just keep it simple!
Got it! But do you have any recommendations for deploying it without an operator?