Skip to content
Percona Everest Documentation

Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

What’s new in Percona Everest 1.10.0

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

Expand to unleash the key updates

📋 Release summary

# Category Description
1. Split-Horizon DNS for Percona Server for MongoDB Enable database administrators to use custom domain names to expose ReplicaSet Pods, both inside and outside the Kubernetes cluster, without conflicting with the default DNS settings.
2. MySQL 8.4 Percona Everest 1.10.0 now supports MySQL 8.4.
3. Percona Monitoring and Management (PMM) 3 Percona Everest 1.10.0 now supports PMM 3.
4. Operator upgrades Support for Percona Operator for MongoDB v1.21.0, Percona Operator for MySQL based on Percona XtraDB Cluster v1.18.0, and Percona PostgreSQL Operator v2.7.0
5. New features Check out the new features introduced in Percona Everest 1.10.0
6. Improvements Discover all the enhancements featured in Percona Everest 1.10.0
7. Bug fixes Find out about all the bugs fixed in Percona Everest 1.10.0
8. Known limitations Discover all the known limitations in Percona Everest 1.10.0

🌟 Release highlights

Seamless access with Split-Horizon DNS for Percona Server for MongoDB

Starting with Percona Everest 1.10.0, we’ve rolled out a new feature: Split-Horizon DNS for Percona Server for MongoDB (PSMDB). This feature enables database administrators to expose ReplicaSet Pods with custom domain names, both inside and outside the Kubernetes cluster, without conflicting with the default DNS configuration.

Why Split-Horizon DNS matters?

Database administrators may sometimes need to expose ReplicaSet Pods in a Percona Operator for a MongoDB cluster so they can connect to them directly. This applies both inside and outside the Kubernetes environment, using custom domain names instead of the default ones generated during cluster creation.

This is useful in scenarios such as:

  • Performing maintenance tasks, like copying data from one ReplicaSet to another cluster.

  • Providing temporary or alternative domain names for direct Pod access without impacting the default DNS configuration.

How to create a Split-Horizon DNS config

Follow these steps to create a new Split-Horizon DNS configuration:

  1. Navigate to the Percona Everest home page and go to Settings > Policies & configurations.

    !image

  2. In the Split-Horizon DNS section, click Configure.

    !image

  3. Click Create configuration and enter the following:

    • Name: The desired name for your Split-Horizon policy.
    • Namespace: The Kubernetes namespace where you want to create the policy.
    • Domain name suffix: A domain represents how your database endpoint is identified (for example, mydb.everest.local).
    • Secret name: Kubernetes Secret that stores the TLS certificate and private key associated with a particular domain.
    • Ca key: Upload your CA private key file.
    • Ca cert: Upload your Certificate Authority (CA) Certificate. A CA certificate is the root or intermediate certificate from the Certificate Authority (CA) that signed your TLS certificate. It helps clients verify that your database’s certificate is valid and trustworthy.

  4. Click Create. Your Split-Horizon DNS policy will be created and appears in the configuration list.

📘 Explore the full capabilities of this feature in our detailed documentation.

Support for MySQL 8.4

Percona Everest 1.10.0 now supports the deployment of MySQL 8.4 clusters. This update allows you to benefit from the latest MySQL version, including enhanced performance, security updates, and an extended lifecycle.

Support for PMM 3

Percona Everest 1.10.0 now supports Percona Monitoring and Management (PMM) 3, enhancing observability and performance insights for database clusters. This ensures improved monitoring capabilities utilizing the latest features and architecture of PMM.

Updated Operators Support

Percona Everest now supports:

  • Percona PostgreSQL Operator v2.7.0.

  • Percona Server for MongoDB Operator v1.21.0.

  • Percona XtraDB Cluster Operator v1.18.0.

New features

  • EVEREST-2239: Added Split-Horizon DNS support for Percona Server for MongoDB (PSMDB).

  • EVEREST-2009: Percona Everest now supports Percona PostgreSQL Operator v2.7.0.

  • EVEREST-2173: Percona Everest now supports Percona Operator for MongoDB v1.21.0.

  • EVEREST-2174: Percona Everest now supports Percona XtraDB Cluster Operator v1.18.0.

Improvements

  • EVEREST-1853: Percona Everest now supports Percona Monitoring and Management (PMM) v3, giving you access to the latest monitoring, alerting, and performance insights. PMM v2 remains supported for backward compatibility.

  • EVEREST-1889: The Overview → Resources section now displays the number of nodes per shard, providing a clearer understanding of resource allocation in sharded deployments at a glance.

  • EVEREST-2302: Menu informational sections are now displayed as plain text. They no longer behave like actions (clickable or hoverable), improving clarity and reducing confusion.

  • EVEREST-2318: The dropdown option Load Balancer has been renamed to LoadBalancer to align with other service types, such as ClusterIP and NodePort.

  • EVEREST-2323: The DB Importers UI now displays credentials in the same order as they appear in Kubernetes secrets and documentation, ensuring a consistent workflow across CLI, docs, and UI.

Bug fixes

  • EVEREST-1865: Point-in-Time Recovery (PITR) details are now displayed correctly when editing PostgreSQL database clusters.

  • EVEREST-1947: Fixed an issue where the Copy URL to Clipboard button in the database details view was not working. Users can now successfully copy the connection URL.

  • EVEREST-2023: The everest operator showed inconsistent behavior in handling resource creation and updates. This issue has now been resolved.

  • EVEREST-2109: Resolved a UI issue that incorrectly showed Point-in-Time Recovery (PITR) for PostgreSQL clusters as disabled after creating on-demand or scheduled backups. PITR was operating correctly, and this update ensures its status is now displayed accurately.

  • EVEREST-2135: Addressed an issue where the S3 bucket field accepted incorrect formats, and the Verify TLS option was unchecked by default. Input validation now ensures the correct S3 formats, and TLS verification is enabled by default.

  • EVEREST-2163: The Pod Scheduling Policy now appears in the Edit Advanced Configuration view even when no rules are defined.

  • EVEREST-2235: Specifying an invalid .spec.engine.version in a DatabaseCluster CRD no longer crashes the Percona Everest Operator. Invalid versions are now handled gracefully with proper validation and error reporting.

  • EVEREST-2237: Creating a database via CRD without specifying monitoring resources no longer causes the Overview page to crash. The page now loads correctly even if monitoring resources are omitted.

  • EVEREST-2259: Resolved an issue where the Connection URL field did not update after enabling the Load Balancer while editing a database. The field now correctly refreshes to reflect the new Load Balancer endpoint once the Host value updates.

  • EVEREST-2278: Percona Everest now correctly manages SSO token expiration, enabling users to continue without clearing their browser cookies.

  • EVEREST-2311: The warning for deleting a load balancer config now clearly states that it can only be deleted if it is not linked to any database, ensuring no impact on the existing databases.

  • EVEREST-2324: Fixed an issue where the everestctl upgrade command did not permit upgrading to the next patch version if a newer minor release is available.

  • EVEREST-2333: Fixed an issue where the documentation link for PITR limitations redirected to an incorrect page.

  • EVEREST-2362: Fixed an issue where a completed restore operation would reappear daily in the Restores tab with an incorrect status after it was manually deleted. Although the cluster functioned normally, the UI continued to show the restore as ongoing.

  • EVEREST-2366: Fixed an issue where the Helm installation command failed to install Percona Everest.

  • EVEREST-1693: Resolved an issue where single-node MongoDB clusters temporarily entered an error state during initial provisioning.

Known limitations

Some limitations apply when using Split-Horizon DNS. For more details, refer to the limitations section.

🚀 Ready to Upgrade?

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

📖 Explore our Upgrade section for the upgrade steps.