Epic Goal

• Work towards moving recover from volume expansion feature to beta/GA.
• Allow users to recover from volume expansion failure if they have resized to a larger/unsupported size.

Based on feedback from api-reviewer's in upstream, we will have to reconsider how to use ResizeStatus to drive the state-machine during expansion operation. The feedback we got from api-reviewer's in general is, ResizeStatus should only be going forward and not backward and it shouldn't flip-flop. We need to consider that feedback when moving this feature to beta.

Why is this important?

• As a requirement of moving volume expansion to GA, we committed to enable a way for users to recover from expansion failures. We are working towards moving this feature to GA.

Scenarios

1. An user expands 100GB PVC to 100TB by mistake and since underlying storage provider does not have that much space available, user have no way to correct that error.
2. User should be able to retry volume expansion to a lower value such as 500GB (down from 100TB)

Acceptance Criteria

• Users should be able to reduce size to a lower value and retry volume expansion.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>