When setting limits VPA will conform to resource policies. It will maintain limit to request ratio specified for all containers.
VPA will try to cap recommendations between min and max of limit ranges. If limit range conflicts with VPA resource policy, VPA will follow VPA policy (and set values outside the limit range).
To disable getting VPA recommendations for an individual container, set mode to "Off" in containerPolicies.
VPA can present memory recommendations in human-readable binary units (KiB, MiB, GiB, TiB) instead of raw bytes, making resource recommendations easier to understand. This feature is controlled by the --humanize-memory flag in the recommender component.
When enabled, memory values in recommendations will be:
- Converted to the most appropriate binary unit (KiB, MiB, GiB, or TiB)
- Displayed with up to 2 decimal places for precision
- Applied to target, lower bound, and upper bound recommendations
For example, instead of seeing a memory recommendation of 262144000 bytes, you would see 250.00Mi.
Note: Due to the conversion to binary units and decimal place rounding, the humanized values may be slightly higher than the raw byte recommendations. For example, 1537 bytes would be shown as "1.50Ki" (1536 bytes). Consider this small difference when doing precise capacity planning.
To enable this feature, set the --humanize-memory flag to true when running the VPA recommender:
--humanize-memory=true