Describe the bug
The PVC autoscaler outputs weird byte values (e.g., 7412376452 bytes) instead of the clean GB units shown in the documentation examples. The documentation shows examples with clean units like 1Gi, 10Gi but the actual output is in raw bytes.
To Reproduce
- Follow the documentation examples which show clean units
- Configure autoscaler with documented settings
- Trigger PVC scaling
- Observe output is
8894851742 bytes instead of clean 8Gi as shown in examples
Expected behavior
PVC should scale to clean GB units as shown in documentation examples: 2Gi → 3Gi → 4Gi
Documentation Inconsistency
- Documentation examples show:
storage: 1Gi, maxCapacity: 10Gi
- Documentation config requires:
scale_up_min_increment: "1000000000" (bytes)
- Actual output:
7412376452 (bytes)
- Expected output:
5Gi (clean units)
Describe the bug
The PVC autoscaler outputs weird byte values (e.g.,
7412376452bytes) instead of the clean GB units shown in the documentation examples. The documentation shows examples with clean units like1Gi,10Gibut the actual output is in raw bytes.To Reproduce
8894851742bytes instead of clean8Gias shown in examplesExpected behavior
PVC should scale to clean GB units as shown in documentation examples:
2Gi→3Gi→4GiDocumentation Inconsistency
storage: 1Gi,maxCapacity: 10Giscale_up_min_increment: "1000000000"(bytes)7412376452(bytes)5Gi(clean units)