-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
None
-
0% To Do, 100% In Progress, 0% Done
-
False
-
-
False
-
XS
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
We GAed recover from resize failures in 4.19 however we need to test and document the pvc.Status.AllocatedResourceStatus field that allows user to track the operation status as described in https://github.com/kubernetes/enhancements/blob/master/keps/sig-storage/1790-recover-resize-failure/README.md
Goals (aka. expected user outcomes)
Users know how to track operation status with status.allocatedResourceStatus
Requirements (aka. Acceptance Criteria):
Field reports what is expected and documented accordingly
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | both |
Classic (standalone cluster) | yes |
Hosted control planes | yes |
Multi node, Compact (three node), or Single node (SNO), or all | all |
Connected / Restricted Network | both |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | all |
Operator compatibility | core storage |
Backport needed (list applicable versions) | no |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | no |
Other (please specify) |
Use Cases (Optional):
As an OCP user I want to track status of the recover from resize failure operation i.e reset a lower capacity value
Questions to Answer (Optional):
We know we don't document it but what is the current testing coverage?
Out of Scope
High-level list of items that are out of scope. Initial completion during Refinement status.
Core feature
Background
Feature itself is already GA, this focuses on the usage of pvc.Status.AllocatedResourceStatus[storage]
Customer Considerations
Improves end user experience
Documentation Considerations
This feature is about documenting how to use the pvc.Status.AllocatedResourceStatus to monitor the status
Interoperability Considerations
Applies to any deployment