Skip to content

Percona Operator for MongoDB 1.13.0

Release Highlights

New Features


  • K8SPSMDB-515 Allow setting requireTLS mode for MongoDB through the Operator to enforce security by restricting each MongoDB server to use TLS/SSL encrypted connections only

  • K8SPSMDB-636 An additional databaseAdmin user was added to the list of system users which are automatically created by the Operator. This user is intended to provision databases, collections and perform data modifications

  • K8SPSMDB-699 Disable automated upgrade by default to prevent an unplanned downtime for user applications and to provide defaults more focused on strict user’s control over the cluster

  • K8SPSMDB-725 Configuring the log structuring and leveling is now supported using the LOG_STRUCTURED and LOG_LEVEL environment variables. This reduces the information overload in logs, still leaving the possibility of getting more details when needed, for example, for debugging

  • K8SPSMDB-719 Details about using sharding, Hashicorp Vault and cluster-wide mode were added to telemetry

  • K8SPSMDB-715 Starting from now, the Opearator changed its API version to v1 instead of having a separate API version for each release. Three last API version are supported in addition to v1, which substantially reduces the size of Custom Resource Definition to prevent reaching the etcd limit

  • K8SPSMDB-709 Make it possible to use API Key to authorize within Percona Monitoring and Management Server as a more convenient and modern alternative password-based authentication

  • K8SPSMDB-707 Allow to set Service labels for replica set, config servers and mongos in Custom Resource to enable various integrations with cloud providers or service meshes

Bugs Fixed

  • K8SPSMDB-702 Fix a bug which resulted in always using the force option when reconfiguring MongoDB member, which is normally recommended only for special scenarios such as crash recovery

  • K8SPSMDB-730 Fix a bug due to which point-in-time recovery was enabled and consequently disabled when setting Percona Backup for MongoDB compression options without checking whether it was enabled in the Custom Resource

  • K8SPSMDB-660 Fix a bug due to which a successful backup could be erroneously marked as failed due to exceeding the start deadline in case of big number of nodes, especially on sharded clusters

  • K8SPSMDB-686 Fix a bug that prevented downscaling sharded MongoDB cluster to a non-sharded replica set variant

  • K8SPSMDB-691 Fix a bug that produced an error in the Operator log in case of the empty SSL Secret name in Custom Resource

  • K8SPSMDB-696 Fix a bug that prevented removing additional annotations previously added under the spec.replsets.annotations field

  • K8SPSMDB-724 Fix a bug which caused the delete-backup finalizer not working causing backups being not deleted from buckets

  • K8SPSMDB-746 Fix a bug due to which the Operator was unable to initialize a three-member replica set with a primary-secondary-arbiter (PSA) architecture

  • K8SPSMDB-762 Fix a bug due to which the Operator was running the replSetReconfig MongoDB command at every reconciliation if arbiter was enabled

Deprecation, Rename and Removal

  • K8SPSMDB-690 CCustom Resource options under the sharding.mongos.auditLog subsection, deprecated since the Operator version 1.9.0 in favor of using replsets.configuration, were finally removed and cannot be used with the Operator

  • K8SPSMDB-709 Password-based authorization to Percona Monitoring and Management Server is now deprecated and will be removed in future releases in favor of a token-based one. Password-based authorization was used by the Operator before this release to provide MongoDB monitoring, but now using the API Key is the recommended authorization method

Supported Platforms

The Operator was developed and tested with Percona Server for MongoDB 4.2.22, 4.4.8, 4.4.10, 4.4.13, 4.4.16, 5.0.2, 5.0.4, and 5.0.11. Other options may also work but have not been tested.

The following platforms were tested and are officially supported by the Operator 1.13.0:

This list only includes the platforms that the Percona Operators are specifically tested on as part of the release process. Other Kubernetes flavors and versions depend on the backward compatibility offered by Kubernetes itself.

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-06-24