Issues
- Storage Class field should not be editable for a DB ClusterEVEREST-1963tigran.papikyan
- Create database button is disabled when monitoring is enabled first timeEVEREST-1962
- Edit monitoring instance does not workEVEREST-1961
- Create an Everest demo deploymentEVEREST-1960
- Database version is not being displayed when creating a new database from backupEVEREST-1959Diana Birsan
- [UI] Auto-expand sections containing fields with error when revisiting a wizard stepEVEREST-1958
- Components page is not displaying the postgresql repo host componentEVEREST-1957
- Disk size field accepts decimals in UI but backend rounds off the valueEVEREST-1956Fábio Da Silva
- Cluster transitions to Down state after entering decimal disk size and triggering invalid StatefulSet updateEVEREST-1955Diana Birsan
- Cli does not display any message for incorrect commandsEVEREST-1954
- PSMDB operator keeps on deleting nonexistent backup jobsEVEREST-1953
- [UI] Disable DB operations during upgrades and disk resizesEVEREST-1952Fábio Da Silva
- [BE] Disable DB operations during upgrades and disk resizesEVEREST-1951Maxim Kondratenko
- Disable DB operations during upgrades and disk resizesEVEREST-1950Fábio Da Silva
- Database gets stuck in Upgrading status if upgrade failsEVEREST-1949Diogo Recharte
- [UI] Component Age isn't displayed properlyEVEREST-1948
- [UI] Copy URL Connection to Clipboard Button Not Working in DB Details ViewEVEREST-1947Diana Birsan
- Add confirmation dialog before performing disk size updateEVEREST-1946
- Cluster UI shows 'Resizing Volumes' state indefinitely despite backend error and 'initializing' statusEVEREST-1945
- [UI] During upgrade of a database, the database operations should be disabledEVEREST-1944Fábio Da Silva
- [UI] Edit modal remains fully interactive during ongoing disk resize operationEVEREST-1943Fábio Da Silva
- Mongodb - UI allows multiple disk resize requests within 6 hours despite AWS EBS rate limitEVEREST-1942
- UI reflects updated disk size prematurely before resize completesEVEREST-1941Diana Birsan
- Mongodb Backups fail if initiated during a disk resize operationEVEREST-1940
- MongoDB cluster temporarily goes down during disk resize operationEVEREST-1939
- Improve the everest-operator kuttl test framework to not use fixed versionsEVEREST-1938
- Upgrade going on a database blocks all changes on other databasesEVEREST-1937
- Mongodb database toggles between Initializing and Down statusEVEREST-1936
- [CLI] Remove deprecated flag `--operator.xtradb-cluster`EVEREST-1935
- Allow PITR Restore based on older backups [PG]EVEREST-1934
- Allow PITR Restore based on older backups [PSMDB]EVEREST-1933
- Allow PITR Restore based on older backups [PXC]EVEREST-1932
- [UI] Improve Diagram View: Default Zoom & Search Functionality for DB Cluster ComponentsEVEREST-1931tigran.papikyan
- Add upgrading stateEVEREST-1930Diogo Recharte
- Validate ResourceQuotas for storage expansionEVEREST-1929
- [BE] Do not allow scaling down disk sizeEVEREST-1928Mayank Shah
- [BE] Do not allow changing storage size after creationEVEREST-1927Mayank Shah
- [Operator] Manual storage scaling for PostgreSQLEVEREST-1926Mayank Shah
- [BE] Implement blacklisting mechanismEVEREST-1925Oksana Grishchenko
- [UI] Update the logout flowEVEREST-1924
- Invalidate session for logged out usersEVEREST-1923Oksana Grishchenko
- Session Management
EVEREST-1922 - DB version upgrade modal should not allow to select the current versionEVEREST-1921Fábio Da Silva
- [UI] Custom number of nodes for PG is not visible properly in cluster overviewEVEREST-1920Diana Birsan
- [BE] Prevent duplicate netmask entries for external accessEVEREST-1919
- [UI] Prevent duplicate netmask entries for external accessEVEREST-1918tigran.papikyan
- E2E tests - Improve uninstall checksEVEREST-1917Resolved issue: EVEREST-1917Edith Erika Puclla Pareja
- Doc - Enable PSMDB sharding section is misleadingEVEREST-1915rasika.chivate
- [UI] Remove focus state after the user clicks out (different places)EVEREST-1914Diana Birsan
- Missing option and information to add more than one backup storage location for PG backup schedulesEVEREST-1913Fábio Da Silva
50 of
Storage Class field should not be editable for a DB Cluster
Description
Environment
None
Attachments
1
is caused by
Details
Details
Details
Smart Checklist
Smart Checklist
Smart Checklist
Created yesterday
Updated yesterday
Activity
Show:
STRs:
Create a new database cluster (e.g., MySQL) and wait until it reaches the ready state.
Navigate to the Database Overview page.
Scroll to the Advanced configuration section.
Click Edit next to the configuration options.
Observe that the Storage Class field appears editable or is shown alongside other editable fields.
Actual Outcome:
The Storage Class field appears to be editable for an existing, running DB cluster.
This implies that users can change it post-creation, which is not supported by Kubernetes and can mislead users.
Expected Outcome:
The Storage Class field should be read-only once the DB cluster is created.
Users should not be allowed to modify the storage class via the UI.
Optionally, a tooltip or info message should clarify:
"the Storage class is defined at creation and cannot be changed later."