Skip to content
Percona Documentation

For help, click the link below to get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona Operator for MongoDB 1.21.0 has been released

Percona Operator for MongoDB 1.21.0 has been released on October 20, 2025.

Try it out using the Quickstart guide.

New features and improvements introduced by this release include:

  • Percona Server for MongoDB 8.0 is now the default version for deploying new clusters. This enables you to enjoy all features and improvements of the latest major version of out of the box.

  • You can now monitor the health and performance of your Percona Server for MongoDB deployment and at the same time enjoy enhanced performance, new features, and improved security that the support for PMM 3 provides. Note that PMM2 support remains in the Operator. The decision what PMM version to use is made based on the configured authentication method. Read more about PMM 3 configuration in the documentation.

  • In addition to arbiters and non-voting nodes, you can now deploy hidden nodes in your Percona Server for MongoDB cluster. These nodes hold a full copy of the data but remain invisible to client applications. They are good for tasks like backups and reporting, since they access the data without affecting normal traffic. Check the documentation for more information about hidden nodes configuration and voting members management by the Operator.

  • The Operator now supports service account key authentication in Google Cloud Storage (GCS), inheriting this functionality from Percona Backup for MongoDB. The configuration of Google Cloud Storage with HMAC keys remains unchanged but is considered deprecated. We encourage you to switch to using service account keys after the upgrade. Read more about GCS support and configuration in the documentation.

  • Improved operational resilience and observability with persistent cluster-level logging for MongoDB Pods. The Operator now supports cluster-level logging ensuring that logs from your mongod instances are stored persistently, even across Pod restarts. Cluster-level logging is currently supported for mongod Pods. All other logs are ephemeral, meaning they will not persist after a Pod restart. Logs are stored for 7 days and are rotated afterwards.

  • Improved backup retention configuration gives you more control over how backups are managed in storage and retained in Kubernetes. Use this new configuration in your Custom Resource:

    schedule:
  - name: "sat-night-backup"
    schedule: "0 0 * * 6"
    retention:
      count: 3
      type: count
      deleteFromStorage: true
    storageName: s3-us-west

    Note that the legacy keep option is now deprecated and mapped to the new retention block for compatibility. If you have both backup.schedule.keep and backup.schedule.retention defined, the backup.schedule.retention takes precedence.

  • Identify the current Operator version associated with Custom Resources via labels. This helps you decide if you need to upgrade it or not.

  • Delegate PVC resizing to an external autoscaler by disabling the built-in resizing functionality. Set spec.enableExternalVolumeAutoscaling option to true in your Custom Resource to prevent the Operator from attempting to resize PVCs. This is useful if you use an external tool to manage volume sizes.

Learn more in Percona Operator for MongoDB 1.21.0 release notes.