Red Hat Bugzilla – Bug 1473584
Decimal memory limits sometimes converted to millibyte form which docs state should not be used
Last modified: 2018-01-07 16:16:24 EST
Description of problem:
Sometimes when setting a memory limit in a DeploymentConfig such as 1.8G, it gets converted to a millibyte value.
The following docs change removed the "m" suffix as it is useless because we cannot manage memory at millibyte granularity, so
do not list the suffix as allowed.
The value that gets converted in the DeploymentConfig should match those listed as valid in the docs. 
Version-Release number of selected component (if applicable):
Sometimes. it may depend on the value being entered.
Steps to Reproduce:
1. oc edit dc <dc>
3. oc get dc <dc> -o yaml | grep memory
If it must be converted to a non decimal value, then it should be the next logical suffix.
Customer see this in 3.2 but it is reproducible in 3.5
I have sent this PR https://github.com/kubernetes/kubernetes/pull/49732 to address this issue.
Still being discussed upstream for fix
I'm lowering the severity on this since it doesn't cause a functional issue, just an aesthetic issue when reading the spec back out.
The workarounds are trivial: either use BinarySI units (Gi,Mi,Ki) or don't use decimal quantities when using DecimalSI unit (G, M, K).