Mongodb Controllers for Kubernetes (MCK)

What is MCK

Mongodb Controllers for Kubernetes (MCK) is a Kubernetes operator that enables users to run MongoDB in Kubernetes.

It supports both MongoDB Community and MongoDB Enterprise Advanced.

For MongoDB Enterprise Advanced, it supports:

• Manages MongoDB Enterprise Advanced deployments in Kubernetes.
• Integrates with MongoDB Ops Manager or Cloud Manager for advanced monitoring, backups, and automation.
• Supports all MongoDB topologies: replica sets, standalone, and sharded clusters. For a full list of capabilities, see the official documentation.

For MongoDB Community, it supports:

• Manages MongoDB Community Server replica sets
• No integration with Ops Manager or Cloud Manager
• Create & manage database users, leveraging SCRAM authentication
• Create & manage custom roles
• Integrate with Prometheus

See more info below for guidance about how MCK differs from other MongoDB Operators, and how to migrate to MCK.

Getting Started & Further Documentation

• For guidance on using the Operator for Enterprise Advanced, please refer to our official documentation.
• For guidance on using the Operator for MongoDB Community Edition, please refer to the guidance in this repository.

License

Customers with contracts that allowed use of the Enterprise Operator will still be able to leverage the new replacement, allowing customers to adopt it without contract changes. The Operator itself is licensed under the Apache 2.0, and a license file included in the repository provides further details. License entitlements for all other MongoDB products and tools remain unchanged (for example Enterprise Server and Ops Manager) - if in doubt, contact your MongoDB account team.

Support, Feature Requests and Community

MCK is supported by the MongoDB Support Team. If you need help, please file a support ticket. If you have a feature request, you can make one on our Feedback Site

You can discuss this integration in our new Community Forum - please use the tag kubernetes-operator

How does MCK differ from the MongoDB Enterprise Kubernetes Operator or MongoDB Community Operator?

MCK unifies MongoDB's support for running MongoDB in Kubernetes into a single Operator.

This unifies:

• MongoDB Enterprise Kubernetes Operator
• MongoDB Community Operator

While early versions of MCK simply bring the capabilities of both previous Operators into a single new Operator, future changes will build on this to more closely align how Community and Enterprise are managed in Kubernetes to offer an even more seamless and streamlined experience.

As an open-source project, MCK allows for community contributions, helping drive quicker bug fixes and ongoing innovation.

Deprecation and EOL for MCO and MEKO

• MongoDB Community Operator End-of-Life (EOL): We will continue best efforts support for 6 months (until November, 2025)
• MongoDB Enterprise Kubernetes Operator End-of-Life (EOL): No change to the current EOL for each individual MEKO version.

No impact on current contracts or agreements.

Migration

Migration from MongoDB Community Operator and MongoDB Enterprise Kubernetes Operator to MCK is seamless: your MongoDB deployments are not impacted by the upgrade and require no changes. Simply follow the upgrade instructions provided in the MCK documentation. See our detailed migration guides:

• Migrating from MongoDB Community Operator
• Migrating from MongoDB Enterprise Kubernetes Operator