Skip to content
Percona Documentation

What’s new in Percona Everest 1.4.0

To begin your journey with Percona Everest, check out the Quickstart Guide for Percona Everest.

Release summary at a glance
Sr. No Release summary Description
1. Helm charts
2. Namespace management
5. New features Check out the new features introduced in Percona Everest 1.4.0
6. Improvements Discover all the enhancements featured in Percona Everest 1.4.0
7. Deprecated APIs Discover all the Deprecated APIs from Percona Everest 1.4.0
8. Bugs Find out about all the bugs fixed in Percona Everest 1.4.0
9. Known limitations Discover all the known limitations in Percona Everest 1.4.0

Release highlights

Capability to configure proxy nodes and define their resource limits

Starting with Percona Everest 1.3.0, we have introduced a new feature that permits you to customize the number of proxies and their resources, including the allocation of CPU and RAM for each proxy. This feature mirrors the existing capability to customize the number of database engine replicas and allocate resources to them.

With this feature, you now have more flexibility to customize the resources allocated to proxies according to your needs, thus providing more control over your Percona Everest deployments.

!image

Optimize MongoDB with sharding in Percona Everest

New features

Improvement

  • EVEREST-1065 [UI] Remove edit button from database list actions

  • EVEREST-1066 [UI] Backups (widget)

  • EVEREST-1210 [UI] Edit advanced configuration (widget + logic)

  • EVEREST-1304 [UI] Select DB type from DB cluster view before opening DB creation wizard

  • EVEREST-1458 [UI] Refactor empty states - tables

  • EVEREST-1546 [UI] Number of proxies/routers/bouncers and their resources should be displayed in dashboard and database overview

  • EVEREST-1683 [UI] Backups on the database overview page should be sorted in descending order by Started date and time

  • EVEREST-1686 Use 24h format

  • EVEREST-1687 [UI] Update button label - upgrade crd version

  • EVEREST-1688 [UI] Number fields can change value on scrolling the page

  • EVEREST-1701 [RBAC] database-cluster-backups resource name matches DB name instead of backup name

  • EVEREST-1702 [RBAC] database-cluster-restores resource name matches DB name instead of restore name

Bugs

  • EVEREST-1187 [UI] PITR is not enabled for postgresql database after creating backup schedules on the Backups page

  • EVEREST-1191 [CLI] Incorrect handling of OIDC issuer URL response parsing

  • EVEREST-1235 [CLI] Improve error messages related to k8s connectivity

  • EVEREST-1254 [CLI] Uninstallation displays a strange code in the end

  • EVEREST-1294 everestctl is not providing error if it cannot connect to k8s cluster

  • EVEREST-1301 [UI] Mongodb backup schedule can’t be created if a schedule with a different backup storage is created in db edit

  • EVEREST-1320 [UI] PITR gap message should come on the Backups page instead of Restores page

  • EVEREST-1352 [UI] All database actions should be disabled if the database is in Deleting status

  • EVEREST-1399 Issue with Resource per Node Selection in Database Creation

  • EVEREST-1407 [RBAC] A user that is not added in the rbac config (not having permissions) can access certain information on Everest

  • EVEREST-1440 [UI] Time lag and Add storage displayed on the Backups page if the user does not have backup storage permissions

  • EVEREST-1518 [RBAC] DB clusters visible and editable for users without permissions for the respective db engine(s)

  • EVEREST-1534 [RBAC] ‘/databases’ page does not show any individual dbs from the policy

  • EVEREST-1565 [UI] Mongodb versions are not sorted and some versions are skipped

  • EVEREST-1593 [UI] Sometimes the Display name and Database version are not displayed in a fresh cluster

  • EVEREST-1594 Scheduled backups start failing after some successful backups for mongodb sharded clusters

  • EVEREST-1604 [RBAC] Create a database from a backup is successful if the user does not have database-engines permissions

  • EVEREST-1608 [UI] Error should be displayed on Resources page if the proxies field has no value

  • EVEREST-1613 Issue with Topology Settings Reverting to “Custom” in Percona Everest UI

  • EVEREST-1615 [CLI] Uninstall fails if a mongodb sharded cluster is in Deleting state

  • EVEREST-1630 “Config Servers” Reset to Default Value of 1 in GUI After Editing Resources

  • EVEREST-1642 [UI] Database version can be changed when restoring to a new database

  • EVEREST-1649 UI - Backup “Add Storage” Button Inactive After Refresh

  • EVEREST-1650 UI - Unable to Create Backup After Adding Storage

  • EVEREST-1694 [RBAC] Backup storages page is empty if user only has access to a single storage

  • EVEREST-1695 [RBAC] Monitoring instances page is empty if user only has access to a single instance

  • EVEREST-1700 Database clusters restarted on creation when PMM monitoring enabled

  • EVEREST-1703 [UI] MongoDB sharded cluster is stuck after selecting not enough config serbvers

  • EVEREST-1712 [UI] Pages become unresponsive after a while

Epic

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.

Community Forum Get a Percona Expert