Skip to content

Percona Kubernetes Operator for Percona Server for MongoDB 1.7.0

Release Highlights

  • This release brings full support for the Percona Server for MongoDB Sharding. Sharding allows you to scale databases horizontally, distributing data across multiple MongoDB Pods, and so it is extremely useful for large data sets. By default of the deploy/cr.yaml configuration file contains only one replica set, but when you turn sharding on, you can add more replica sets with different names to the replsets section.

  • It is now possible to clean up Persistent Volume Claims automatically after the cluster deletion event. This feature is off by default. Particularly it is useful to avoid leftovers in testing environments, where the cluster can be re-created and deleted many times. Support for custom sidecar containers. The Operator makes it possible now to deploy additional (sidecar) containers to the Pod. This feature can be useful to run debugging tools or some specific monitoring solutions, etc. The sidecar container can be added to replsets, sharding.configsvrReplSet, and sharding.mongos sections of the deploy/cr.yaml configuration file.

New Features


  • K8SPSMDB-335: Operator can now automatically remove old backups from S3 if retention period is set

  • K8SPSMDB-330: Add support for runtimeClassName Kubernetes feature for selecting the container runtime

  • K8SPSMDB-306: It is now possible to explicitly set the version of MongoDB for newly provisioned clusters. Before that, all new clusters were started with the latest MongoDB version if Version Service was enabled

  • K8SPSMDB-370: Fix confusing log messages about no backup / restore found which were caused by Percona Backup for MongoDB waiting for the backup metadata

  • K8SPSMDB-342: MongoDB container liveness probe will now use TLS to follow best practices and remove noisy log messages from mongod log

Bugs Fixed

  • K8SPSMDB-346: Fix a bug which prevented adding/removing labels to Pods without downtime

  • K8SPSMDB-366: Fix a bug which prevented enabling Percona Monitoring and Management (PMM) due to incorrect request for the recommended PMM Client image version to the Version Service

  • K8SPSMDB-402: running multiple replica sets without sharding enabled should be prohibited

  • K8SPSMDB-382: Fix a bug which caused mongos process to fail when using allowUnsafeConfigurations=true

  • K8SPSMDB-362: Fix a bug due to which changing secrets in a single-shard mode caused mongos Pods to fail

Get expert help

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services. Join K8S Squad to benefit from early access to features and “ask me anything” sessions with the Experts.

Last update: 2024-05-17