Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update README.md to show latest release #115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update README.md to show latest release #115
Changes from all commits
2b89559
3006fdf
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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:
For MongoDB Community, it supports:
See more info below for guidance about how MCK differs from other MongoDB Operators, and how to migrate to MCK.
Getting Started & Further Documentation
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:
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
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 migration guidance. See our detailed migration guides: