Looking for a Simple Helm Chart for Single MongoDB Instances

Keep in mind that whoever is responsible for maintaining the MongoDB instance will have to ensure it remains operational. If something goes wrong, they will have to deal with it, and that might make the overhead of using an operator more justified. It might benefit your team to consider this in the long run.

Managing an operator typically involves less overhead than trying to manage the database itself without one. The operator helps streamline operations in the long run, especially if you plan to expand in the future.

Have you thought about whether your current deployment strategy is reusable? In a large organization, handling everything at scale can get tricky. While operators help manage issues like pod disruptions and backups effectively, I'd recommend checking out the Percona MongoDB Operator if you decide to go that route. But if you’re set on avoiding that, look for a lightweight Helm chart that meets your specific needs.

You might find it easier to just run a StatefulSet instead of managing an operator. If you're simply looking to have a single node for MongoDB without the complications of clustering or backups, a StatefulSet can handle that for you. If you need more complex features, consider using cloud solutions or VMs outside of Kubernetes.