The Operator was developed and tested with Percona Server for MongoDB 4.4.18, 5.0.14, and 6.0.4. Other options may also work but have not been tested.
The MMAPv1 storage engine is no longer supported for all MongoDB versions starting from the Operator version 1.6. MMAPv1 was already deprecated by MongoDB for a long time. WiredTiger is the default storage engine since MongoDB 3.2, and MMAPv1 was completely removed in MongoDB 4.2.
Officially supported platforms¶
The following platforms were tested and are officially supported by the Operator 1.14.0:
Google Kubernetes Engine (GKE) 1.22 - 1.25
Amazon Elastic Container Service for Kubernetes (EKS) 1.22 - 1.24
OpenShift Container Platform 4.10 - 4.12
Azure Kubernetes Service (AKS) 1.23 - 1.25
Other Kubernetes platforms may also work but have not been tested.
A cluster running an officially supported platform contains at least 3 Nodes and the following resources (if sharding is turned off):
- 2GB of RAM,
- 2 CPU threads per Node for Pods provisioning,
- at least 60GB of available storage for Private Volumes provisioning.
Consider using 4 CPU and 6 GB of RAM if sharding is turned on (the default behavior).
Also, the number of Replica Set Nodes should not be odd if Arbiter is not enabled.
Use Storage Class with XFS as the default filesystem if possible to achieve better MongoDB performance.
For free technical help, visit the Percona Community Forum.
To report bugs or submit feature requests, open a JIRA ticket.
For paid support and managed or consulting services , contact Percona Sales.