Frequently Asked Questions
As it is well known, the Kubernetes approach is targeted at stateless applications but provides ways to store state (in Persistent Volumes, etc.) if the application needs it. Generally, a stateless mode of operation is supposed to provide better safety, sustainability, and scalability, it makes the already-deployed components interchangeable. You can find more about substantial benefits brought by Kubernetes to databases in this blog post.
The architecture of state-centric applications (like databases) should be composed in a right way to avoid crashes, data loss, or data inconsistencies during hardware failure. Percona Kubernetes Operator for Percona Server for MongoDB provides out-of-the-box functionality to automate provisioning and management of highly available MongoDB database clusters on Kubernetes.
The best place to discuss Percona Kubernetes Operator for Percona Server for MongoDB with developers and other community members is the community forum.
If you would like to report a bug, use the Percona Kubernetes Operator for Percona Server for MongoDB project in JIRA.
As you have noticed, the installation section of docs contains both quickstart and advanced installation guides.
The quickstart guide is simpler. It has fewer installation steps in favor of predefined default choices. Particularly, in advanced installation guides, you separately apply the Custom Resource Definition and Role-based Access Control configuration files with possible edits in them. At the same time, quickstart guides rely on the all-inclusive bundle configuration.
At another point, quickstart guides are related to specific platforms you are going to use (Minikube, Google Kubernetes Engine, etc.) and therefore include some additional steps needed for these platforms.
Generally, rely on the quickstart guide if you are a beginner user of the specific platform and/or you are new to the Percona Server for MongoDB Operator as a whole.
Percona Operator for Percona Server for MongoDB provides a ready-to-use installation of the MongoDB-based database cluster inside your Kubernetes installation. It works with Percona Server for MongoDB 3.6, 4.0, 4.2, and 4.4, and the exact version is determined by the Docker image in use.
Percona-certified Docker images used by the Operator are listed here. For example, Percona Server for MongoDB 4.4 is supported with the following recommended version: 4.4.2-4. More details on the exact Percona Server for MongoDB version can be found in the release notes (4.4, 4.2, 4.0, and 3.6).