Issues

PSMDB restored cluster stuck in restoring state

[UI] user-specified DB name gets reset to the auto-generated one when creating a DB

[UI] Estimated CPU and memory/disk is the same for 1, 2, 3 nodes and memory/disk values are unclear, missing

PG Cluster stuck in initializing with PMM monitoring turned on

[UI] UI should display the number of nodes, pods, replica for a database cluster

Unable to create DB cluster with External Access Enabled

PG DB Cluster Backup issue (CR + Delete)

[CLI] Cli does not have a flag to specify backup name, backup storage creation fails

Backup and pods are not deleted if the db cluster is deleted

[UI] For backup, the backup name and for restore, the display name should be unique or random

[UI] Restore/create new db option should be disabled for failed backups

[UI] During backup, restore/create new db option should be disabled

[UI] Backup failed but no error is displayed

[UI] Create immediate backup displays unclear error message

[UI] Add Backup Storage disappears on losing focus

Restore of a backup to a new cluster fails

[UI] The UI displays mysql database options when only mongodb, postgres operators are installed

[CLI] Cli is displaying date and time in logs as floating point number

Manual command to copy secrets to the new database should be removed

[UI] Incorrect command during the backup restore of a new database

Minikube not available - docker compose dev-latest

[UI] After Edit, the UI displays that a new database is being created

Unable to create Backups for DB clusters (PXC, PG and MongoDB)

Cli is not able to connect to the backup storage, when Everest is run using dev-latest in quickstart.yml

[UI] Database status is incorrect after Resume

[UI] Error message is not clear if Suspend, Resume, Restart cannot be done

[UI] After Suspend the Resume option is not displayed

[UI] For Suspend, Resume, Restart, there is no response displayed

[UI] Database does not come up if the number of nodes are changed

[UI] Database does not come up if the version is changed

[CLI] Kubernetes cluster is not registered in backend if backup storage creation fails

[BE] Create backup for non-existing DB cluster, returning "Created 201" response

Database cluster created by Cli cannot be edited by UI

[CLI] Incorrect error when a kubernetes cluster is deleted and it does not exist

Pods and services go down by themselves

[BE] Error messages should be improved for create backup storage api

[UI] Incorrect status displayed if haproxy pod, service goes down

[CLI] Errors should not contain exceptions or stack traces

[FE] Everest not showing correct information if no K8 cluster is registered

[UI] Backup storage cannot be added for Google and Azure Cloud Storage

Long name DB cluster failing with error

[UI] Databases Status is not updated by Everest