Skip to content
Percona Operators Documentation

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

Get help from Percona

Percona Kubernetes Operator for Percona Server for MongoDB 1.6.0

New Features

Note

Monitoring with PMM v.1 configured according to the unofficial instruction will not work after the upgrade. Please switch to PMM v.2.

Improvements

  • K8SPSMDB-258: Add support for Percona Server for MongoDB version 4.4

  • K8SPSMDB-319: Show Endpoint in the kubectl get psmdb command output to connect to a MongoDB cluster easily

  • K8SPSMDB-257: Store the Operator version as a crVersion field in the deploy/cr.yaml configuration file

  • K8SPSMDB-266: Use plain-text passwords instead of base64-encoded ones when creating System Users secrets for simplicity

Bugs Fixed

  • K8SPSMDB-268: Fix a bug affecting the support of TLS certificates issued by cert-manager , due to which proper rights were not set for the role-based access control, and Kubernetes versions newer than 1.15 required other certificate issuing sources

  • K8SPSMDB-261: Fix a bug due to which cluster pause/resume functionality didn’t work in previous releases

  • K8SPSMDB-292: Fix a bug due to which not all clusters managed by the Operator were upgraded by the automatic update

Removal

  • The MMAPv1 storage engine is no longer supported for all MongoDB versions starting from this version of the Operator. 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.

Note

Upgrade of the Operator from 1.5.0 to 1.6.0 will fail if MMAPv1 is used, but MongoDB cluster will continue to run. It is recommended to migrate your clusters to WiredTiger engine before the upgrade.

Last update: 2025-04-25
Was this page helpful?