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
Details
$ kubectl version
# paste output here
1.31
Cloud provider
Details
OS version
Details
# 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
Details
Container runtime (CRI) and version (if applicable)
Details
Related plugins (CNI, CSI, ...) and versions (if applicable)
Details
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
Details
1.31
Cloud provider
Details
OS version
Details
Install tools
Details
Container runtime (CRI) and version (if applicable)
Details
Related plugins (CNI, CSI, ...) and versions (if applicable)
Details