You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
Yes. VPA memory recommendations are applied as kilobytes (k, the non-binary 1000 byte) and it's not very relevant to the humans that are reading the podspec later.
Describe the solution you'd like.:
Convert to the units to highest SI suffix without decimal places.
Describe any alternative solutions you've considered.:
N/A
The text was updated successfully, but these errors were encountered:
Hi all, I tried with 1.3.0 image with "--humanize-memory=true" today, but found the MEM value now having more digits with the unit "milibyte". This value looks to align with the code design 272063528960/1000/1024/1024=259.46Mi, but seems more unreadable. Is there some configuration I missed?
$ k get verticalpodautoscalers.autoscaling.k8s.io -n logging fluent-bit-service
NAME MODE CPU MEM PROVIDED AGE
fluent-bit-service Initial 126m 272063528960m True 2d21h
Which component are you using?:
VPA
Is your feature request designed to solve a problem? If so describe the problem this feature should solve.:
Yes. VPA memory recommendations are applied as kilobytes (
k
, the non-binary 1000 byte) and it's not very relevant to the humans that are reading the podspec later.Describe the solution you'd like.:
Convert to the units to highest SI suffix without decimal places.
Describe any alternative solutions you've considered.:
N/A
The text was updated successfully, but these errors were encountered: