Fix format_quantity precision and emit canonical decimal output#2625
Merged
kubernetes-prow[bot] merged 1 commit intoJul 7, 2026
Conversation
Signed-off-by: Artem Muterko <artem@sopho.tech>
kubernetes-prow
Bot
added
release-note
kubernetes-prow
Bot
added
size/M
kubernetes-prow
Bot
added
the
lgtm
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: archy-rock3t-cloud, roycaihw The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubernetes-prow
Bot
added
the
approved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it:
For the milli, micro and nano suffixes,
format_quantitybuilt a Decimal from a float and returned imprecise values in scientific notation, which are not valid Kubernetes quantities. It now scales withDecimal(base) ** exponentand formats in plain decimal, matchingparse_quantity, and no longer ignoresquantize=Decimal(0).Which issue(s) this PR fixes:
Fixes #2624
Does this PR introduce a user-facing change?