KubeBlocks for
MongoDB
MongoDB is the leading document-oriented NoSQL database, designed for flexibility and scalability. Its JSON-like document model, powerful aggregation framework, and horizontal scaling make it ideal for content management, IoT, and mobile applications.
Supported versions
Available on
AWS
Azure
GCP
OCI
OpenShiftDatabases
MySQL
PostgreSQL
Oracle
SQL Server
Redis
ClickHouseVector & AI
Milvus
ElasticsearchMessage queues
KafkaOthers
etcdExtend database engines like plug-ins
KubeBlocks provides unified database operations through its addon-based architecture. With KubeBlocks Enterprise, access over 15 seamless integrations to scale your database services.
One control plane, consistent operations across all engines — powered by the addon mechanism.
Run MongoDB with guided lifecycle, topology control, and recovery
From replica-set provisioning and horizontal scaling to Switchover, monitoring, audit history, backup, and cleanup, the MongoDB addon helps teams operate production-ready document databases from one console.
Lifecycle
Launch MongoDB replica sets and keep lifecycle context visible
Deploy MongoDB with the version, replica count, resource profile, and storage settings your team needs, then keep cluster status, topology, and routine service actions close at hand from the same workspace.
- Use the create wizard to choose MongoDB version, Replica Set topology, compute profile, and storage before launch.
- Land on an Overview page that keeps primary-secondary layout, version, sizing, and connection context visible after provisioning.
- Handle restart, stop, and start workflows from the MongoDB detail page while task progress remains tied to the running cluster.

The create wizard helps teams launch MongoDB with Replica Set topology, version, sizing, and storage choices already aligned with operational standards.

After provisioning, the Overview page keeps topology, role layout, sizing, and runtime status visible from the first day of operation.
Scale
Scale replica capacity with a guided Horizontal Scaling workflow
Expand MongoDB replica capacity from the same cluster workspace so teams can grow read throughput and resilience without dropping into manual infrastructure changes.
- Open Horizontal Scaling directly from the running MongoDB cluster.
- Add more secondaries while keeping replica initialization and topology change visible in context.
- Review scaling progress from the same operational view used for health checks and lifecycle control.

Horizontal Scaling makes replica growth visible on the live MongoDB topology instead of hiding it behind infrastructure tooling.
SwitchOver
Move the primary role with a topology-aware Switchover
Perform planned MongoDB primary changes with the real replica set in view so teams can validate leadership movement and resulting node roles with less guesswork.
- Run Switchover from the cluster workspace when maintenance or role movement is required.
- Verify which member becomes the new primary immediately after the operation completes.
- Keep planned role transitions separate from scaling, backup, and monitoring workflows.

Switchover keeps the new primary and remaining secondaries visible on the same MongoDB topology view for fast post-change validation.
Parameter
Review runtime parameter exposure from the Parameters page
Keep MongoDB configuration visibility separate from lifecycle and scaling workflows so teams can confirm what runtime settings are exposed for the selected deployment before planning changes.
- Open the Parameters page directly from the MongoDB workspace when reviewing configuration scope.
- Check whether the current MongoDB topology or version exposes editable runtime settings.
- Give platform teams a clearer place to validate configuration availability before change windows.

The Parameters page helps teams verify whether editable MongoDB runtime settings are exposed for the current deployment before they plan configuration work.
Accessibility
Share endpoint and connection details from the Overview page
Keep MongoDB connectivity evidence close to the running cluster so application teams can confirm reachable endpoints and server address details without switching to a separate networking console.
- Review Connection Information directly from the MongoDB Overview page.
- Confirm the available service endpoint and server address for the running replica set.
- Reduce handoff friction when teams need validated connection details for application onboarding.

Connection Information keeps MongoDB endpoint and server-address visibility in the same workspace used to operate the replica set.
Observability
Inspect MongoDB health through Cluster Monitor and Runtime Log
Monitor replica-set health, resource usage, and live service events from built-in metrics and log views so troubleshooting stays close to the workload.
- Use Cluster Monitor to review MongoDB charts, filters, and resource signals from the real cluster context.
- Inspect Runtime Log output for live `NETWORK` and `ACCESS` activity when diagnosing service behavior.
- Keep metrics and logs available inside the same control plane used for lifecycle and scaling operations.

Metrics bring MongoDB health and resource trends into the console so teams can review runtime behavior without leaving cluster context.

Runtime Log surfaces real MongoDB service activity such as connection and access events for faster troubleshooting.
Audit
Track operational history from the Tasks page
Keep a clear execution trail for MongoDB maintenance and topology changes so teams can review what ran, when it ran, and which actions completed successfully.
- Review Horizontal Scaling, Switchover, and Restart records from the Tasks page.
- See status and timing details for completed operational work in one place.
- Improve post-change review and accountability for MongoDB service operations.

Task history turns MongoDB maintenance and topology changes into a clear operational record that teams can review after each change window.
Backup
Protect MongoDB replica sets with built-in backup and restore flows
Keep MongoDB protection points and recovery workflows inside the addon experience so teams can validate backup status and open restore planning from the same workspace.
- Review completed full backups together with size, status, and backup repository details.
- Open the restore wizard with a real backup set already selected when recovery validation is needed.
- Treat backup and restore as first-class MongoDB operations instead of external runbooks.

The Backups page keeps MongoDB protection status, backup size, and repository context visible from the same operational workspace.

The restore wizard guides teams through MongoDB recovery settings step by step when they need validation or incident-response readiness.
Cleanup
Retire clusters safely after Delete Protection is cleared
Make MongoDB cleanup deliberate by clearing Delete Protection first, then removing the cluster from the same operational workflow once the team is ready to release resources.
- Disable Delete Protection before a MongoDB cluster can be removed.
- Keep the final cleanup action close to the cluster context used for lifecycle and backup review.
- Reduce accidental teardown risk while still giving teams a fast path to reclaim test resources.

Delete becomes executable after protection is cleared, giving teams a clear final checkpoint before MongoDB resources are removed.
Ready to build your own DBaaS on Kubernetes?
Talk to our team and see how KubeBlocks Enterprise can help you consolidate databases, strengthen security, and reduce operational costs.

