Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

MySQL Manual Storage Scaling

Description

User Story:
As a user managing a MySQL database, I want to be able to increase the disk size from the "Edit Resources" modal, so that I can scale storage based on my growing data needs.

Context:
Currently, MySQL users can modify CPU and Memory but cannot adjust disk size after database creation. This limitation can cause issues as storage needs grow, requiring users to migrate to a larger instance manually. By allowing disk size to be increased, we improve flexibility and reduce operational overhead.

Acceptance Criteria:

  • Users can access the "Edit Resources" modal from the database overview screen.

  • The disk size field is editable, allowing only an increase in size.

  • The updated disk size is reflected in the UI.

  • After updating the disk size, the DB state moves to the “initializing” but eventually moves back to the “ready” state.

  • If the storage class used doesn’t support allowVolumeExpansion, the editing of the disk size should be disabled with an appropriate message explaining why it’s disabled.

Design (Figma link):

Tech Documentation:

Limitations:

Attachments

11
100% Done
Loading...

Activity

Edith Erika Puclla Pareja 
March 28, 2025 at 10:50 AM
(edited)

I tested this new feature branch with the following scenarios:

  • In the case of EKS, the ALLOWVOLUMEEXPANSION is in False, we need to change it by adding

  • I created a database and scaled it; it worked as expected.

Error handling tests:

⚠️ Warning

Before starting a storage increase, a warning informs users the operation is irreversible.

🔴 Error Banner on Storage Scaling Failure

User attempts to scale storage but the operation fails

 

If resizing fails, the database status remains in a “Resizing volumes” state.

  • This state reflects ongoing attempts by the CSI driver to resize the volume.

  • Logs or status events should capture these repeated resizing attempts.

Note: This will be added as a limitation in the documentation

UI validation of the empty value


I tested this ticket, if there is anything that is missing in error handling, please let me know, if no we can move it to Ready to merge

Diogo Recharte 
March 28, 2025 at 7:30 AM

The branch situation got a bit messy and I ended up creating a feature build with the wrong helm chart branch. Here’s the FB with all the correct branches:

Diogo Recharte 
March 27, 2025 at 12:59 PM

Fábio Da Silva 
March 27, 2025 at 11:11 AM

Diogo Recharte 
March 26, 2025 at 11:25 PM

New FB that includes the improvements/fixes of , , , the new error banner in the DB overview page and the “Upscaling disk size is an irreversible action” warning in resource editing modal:

Unresolved

Details

Assignee

Reporter

QA

Story Points

Fix versions

Priority

Parent

Created February 11, 2025 at 6:48 PM
Updated March 28, 2025 at 6:52 PM