The resources.limits.memory unit is automatically converted. Why cannot the unit be displayed as configured?

[Black-max12138]

What happened?

When resources.limits.memory is set to 1237.3Mi, the actual pod is 1297403084800 m by running the kubectl command, which is difficult to understand.

What did you expect to happen?

Resources.limits.memory can be displayed based on the configured value and unit.

How can we reproduce it (as minimally and precisely as possible)?

Set resources.limits.memory to 1237.3Mi and run the kubectl command to check the value.

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
# paste output here

1.31

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Ritikaa96]

I think this helps us to understand what is the actual limit , if it shows in mentioned unit , the value will only show till particular decimal places.

[Ritikaa96]

/sig storage
/sig node

[Ritikaa96]

but there has been mention of why Mi value usage created some issue like : kubernetes/kubernetes#128684

/sig api-machinery

[sftim]

/remove-sig storage node api-machinery
/sig cli

/transfer kubectl

IMO, the choice of conversion function (for display) is one made by the kubectl tool