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

What’s new in Percona Everest 1.6.0

➡️ New to Percona Everest? Get started with our Quickstart Guide.

🔑 Expand to unleash the key updates
# Release summary Description
1. Manual storage scaling Increase the capacity of your storage through manual storage scaling
2. MongoDB: Major DB updates Support for major version upgrades of MongoDB
3. Operator Upgrades Support for Percona Operator for PostgreSQL 2.6.0 and PostgreSQL 17
4. Removed support for PostgreSQL 12 Percona Everest 1.6.0 discontinues support for PostgreSQL 12
5. Google Container Registry (GCR) deprecation Deprecation of GCR starting May 20, 2025
6. New features Check out the new features introduced in Percona Everest 1.6.0
7. Improvements Discover all the enhancements featured in Percona Everest 1.6.0
8. Bugs Find out about all the bugs fixed in Percona Everest 1.6.0
9. Known limitation Discover all the known limitations in Percona Everest 1.6.0

🌟 Release highlights

Scale your storage with ease with Percona Everest 1.6.0

Starting with Percona Everest 1.6.0, you can leverage manual storage scaling to increase the capacity of your database, offering greater control over resource allocation as your needs evolve.

Prerequisites for storage scaling

How to modify storage capacity

To increase the DISK for a database, go to the Percona Everest home page and select your desired database. Then, navigate to Overview > Resources > Edit and enter the new value for DISK (in Gi).

!image

🔍 If you want to explore this topic in depth, check out our detailed documentation!

Seamless major version upgrades for MongoDB

Percona Everest 1.6.0 introduces support for major version upgrades of MongoDB, enabling you to upgrade your databases with minimal downtime and disruption. This enhancement ensures your applications remain secure, performant, and compliant with the latest MongoDB features.

To upgrade your MongoDB database, navigate to the Percona Everest homepage and select the database you wish to upgrade. On the Overview page, locate the DB Details panel and click Edit next to Basic Information. Select the desired version and click Upgrade to begin the process.

!image

!image

🔍 For a deep dive into this topic, refer to our documentation.

Support for PostgreSQL Operator 2.6.0 and PostgreSQL 17

Percona Everest 1.6.0 now includes support for Percona Operator for PostgreSQL 2.6.0 and PostgreSQL 17.

🛑 Removed support for PostgreSQL 12

Percona Everest 1.6.0 no longer supports PostgreSQL 12.

Action required

To upgrade to Percona Everest 1.6.0, you must first migrate your clusters to a supported PostgreSQL version (13 or higher).

Migration Guide: Follow our PostgreSQL migration procedure for a step-by-step guide to a seamless upgrade.

🛑 Google Container Registry (GCR)

GCR deprecation

GCR is set to be deprecated, with its official shutdown scheduled for May 20, 2025.

All Percona Everest versions prior to 1.4.0 depend on images hosted on the Google Container Registry (GCR). These images will become unavailable after the shutdown date: May 20, 2025.

Impact

Percona Everest versions older than 1.4.0 will cease to function after this date.

Action required

We strongly recommend upgrading to Percona Everest version 1.4.0 or later as soon as possible. If you do not upgrade, Percona Everest will no longer function.

For more details, refer to the Container Registry Deprecation documentation.

New features

  • EVEREST-1870, EVEREST-1871, EVEREST-1872: Starting with Percona Everest 1.6.0, you can leverage manual storage scaling to increase the capacity of your storage for MySQL, MongoDB, and PostgreSQL databases, respectively.

  • EVEREST-1841: Percona Everest 1.6.0 introduces support for major version upgrades of MongoDB, enabling you to upgrade your databases with minimal downtime and disruption.

  • EVEREST-1843 : Percona Everest 1.6.0 includes support for Percona Operator for PostgreSQL 2.6.0 and PostgreSQL 17.

  • EVEREST-1986: The Helm chart now supports deploying an Ingress resource to expose the Percona Everest server externally. This enhancement enables seamless integration with ingress controllers (e.g., NGINX) to manage access to the Percona Everest UI and APIs.

  • EVEREST-1852: PMM can now be deployed as a sub-chart by setting pmm.enabled=true. As the PMM chart currently lacks support for namespace overrides, it will be deployed in the designated release namespace: everest-system.

    Also, PMM can now be fully configured from the Everest chart. This can be done by specifying options under the pmm field. This simplifies deployment management, offering greater flexibility and control for Helm-based workflows.

Improvements

  • EVEREST-1202: We’ve refined the table header icons by removing the focus state when users click outside for an enhanced UX.

  • EVEREST-1280: We’ve moved the Storage class field to the Advanced Configurations page for better organization and usability.

  • EVEREST-1312: The installation log now displays the same operator names as selected in the wizard for consistency and clarity.

  • EVEREST-1711: We’ve enhanced the database creation wizard by removing the final confirmation step, which improves user flow and decreases the number of clicks needed to create a database.

  • EVEREST-1921: Updated the database version upgrade modal to prevent selection of the current version, ensuring only valid upgrade options are available.

  • EVEREST-1930: We have introduced a distinct Upgrading state that clearly indicates when a database upgrade is taking place.

  • EVEREST-1912: The Storage Class used by a database cluster is now prominently displayed on the database Overview page, enhancing visibility and making it easier for users to access configuration details directly within the UI.

Bugs

  • EVEREST-765: We have fixed an issue that caused Point-In-Time Recovery (PITR) to be disabled after the database was suspended and then resumed.

  • EVEREST-1350: The UI now displays the IP address along with the netmask, ensuring consistency with the backend format.

  • EVEREST-1374: We have identified and addressed an inconsistency in the logic governing the naming restrictions for backup storage and monitoring endpoints.

  • EVEREST-1625: Point-In-Time Recovery (PITR) options were not visible in the UI when no scheduled backups were in place. This occurred even if the most recent backup was completed successfully and PITR was enabled. This issue has been resolved now.

  • EVEREST-1763: When modifying the network topology by reducing the configuration from three nodes to a single node, no error message was displayed. This issue has been resolved, and an error message now appears, indicating that downscaling is not possible.

  • EVEREST-1798: Resolved an issue where the PostgreSQL cluster was repeatedly initialized, leading to backup failures in specific scenarios.

  • EVEREST-1911: Fixed an issue where an empty state briefly appeared before the first DB cluster was displayed.

  • EVEREST-1920: Fixed a UI issue where the custom number of nodes for PostgreSQL was not displaying correctly in the cluster overview.

  • EVEREST-1985: Resolved an issue preventing PITR-based recovery when backup schedules were added after the PostgreSQL database was created.

  • EVEREST-1979: Addressed an issue where the database engine upgrade unexpectedly modified the backup schedule time.

  • EVEREST-1959: The database version was not displayed when creating a new database from a backup. This issue has been resolved now.

  • EVEREST-1963: The storageclass field associated with a database cluster is now non-editable to ensure consistency.

  • EVEREST-1978: The PITR location was initially set incorrectly during backup restoration but has now been corrected.

Known limitation

PostgreSQL 17.2 CVE-2025-1094 Vulnerability

Images based on PostgreSQL 17.2 are affected by CVE-2025-1094 — a critical vulnerability in libpq that can lead to SQL injection via the PostgreSQL terminal.

Resolution

Support for PostgreSQL 17.4 is now available, featuring critical security and stability updates, particularly addressing the CVE identified in version 17.2.

We strongly recommend using PostgreSQL version 17.4 instead of 17.2 to take advantage of the latest fixes and improved security features.

🚀 Upgrade now

Upgrade to Percona Everest 1.6.0 to access these new features and improvements.

🔍 Explore our documentation for the upgrade steps.