Red Hat Bugzilla – Bug 1290241
[RFE] expand storage on persistent volume without losing data
Last modified: 2017-09-18 15:21:20 EDT
- What is the nature and description of the request?
As an admin I need the ability to expand the storage setup on a persistent volume, without losing the existing data that I already have.
- Why does the customer need this? (List the business requirements here)
The docker images they have pushed to their registry are taking up too much space. A possible fix for this scenario is to increase the size of the registry.
- How would the customer like to achieve this? (List the functional requirements here)
The ability to expand the Persistent Volume without damaging the data inside the existing PV.
- Is there already an existing RFE upstream or in Red Hat Bugzilla?
Not that I could find
- List any affected packages or components.
This is a feature request for "resizing a volume", for which we have a Trello card.
This card is being tracked here - https://trello.com/c/WC1urO9c/138-21-provide-a-means-to-increase-the-storage-capacity-of-a-pv-openshift-online-ops-rfe
It hasn't moved yet as it will only get worked on after the core storage functionality refactoring, storage classes and dynamic provisioning is complete.
Do you have a specific bug (or several bugs) or trello(s) that we can put as blocking on this bug? As you indicated that this won't be worked until "core storage functionality refactoring, storage classes and dynamic provisioning is complete."
Eric, I think a better approach is to track the feature card https://trello.com/c/02MHzcR0/272-feature-support-the-ability-to-resize-a-persistent-volume (which is now linked to the work item card in the description) and see which OpenShift release it is scheduled for. At present, it is proposed for OpenShift 3.5, but we have yet to do release planning for that. In reality, we need to start with a Spike to actually figure out how we're going to address this problem. Once we do that, we need to build community consensus around the approach and only once that happens, does the rough timeline regarding when this will land in an OpenShift release, start to take shape.
*** Bug 1407011 has been marked as a duplicate of this bug. ***