-
Feature Request
-
Resolution: Done
-
Normal
-
None
-
openshift-4.15
-
None
1. Proposed title of this feature request:
Allow disabling over-provisioning in LVMS as a day 2 operation
2. What is the nature and description of the request?
Currently, in OCP 4.15, it is only possible to disable over-provisioning in Logical Volume Management for Kubernetes (LVMS) at the time of LVM cluster creation by setting the `thinPoolConfig.overprovisionRatio` field to 1. Attempting to modify this setting after cluster creation results in the error:
admission webhook "vlvmcluster.kb.io" denied the request: ThinPoolConfig.OverprovisionRatio is invalid: ThinPoolConfig can not be changed
This feature request seeks to enable users to disable over-provisioning as a day 2 operation, allowing for flexibility in managing storage configurations after initial setup.
3. Why does the customer need this? (List the business requirements here)
- Flexibility: Customers require the ability to adjust storage configurations after initial deployment to meet changing business needs or performance requirements.
- Operational Efficiency: Enabling day 2 operations for disabling over-provisioning reduces the need for LVM cluster recreation.
4. List any affected packages or components:
- OpenShift Container Platform (OCP) version 4.15 and above.
- Logical Volume Managemer Storage (LVMS) components.
- is triggering
-
OCPSTRAT-1370 LVMS: make ThinPoolConfig.ThinPoolConfig.OverprovisionRatio editable
-
- Backlog
-