Make docs for new flags more clear

[rancher-max]

Types of Changes

docs for #1463

Verification

N/A

Linked Issues

#1525

Further Comments

More clear since config.yaml is our recommended approach of installing and specifying the flag multiple times there only uses the last value specified.

[rancher-max]

Had to push an update to the documented memory values, otherwise we hit this error:

Aug 12 18:24:07 maxt2 rke2[43738]: time="2021-08-12T18:24:07Z" level=error msg="error parsing memory request for static pod kube-apiserver: quantities must match the regular expression '^([+-]?[0-9.]+)([eEinumkKMGTP]*[-+]?[0-9]*)$'"
Aug 12 18:24:07 maxt2 rke2[43738]: time="2021-08-12T18:24:07Z" level=error msg="error parsing memory limit for static pod kube-apiserver: quantities must match the regular expression '^([+-]?[0-9.]+)([eEinumkKMGTP]*[-+]?[0-9]*)$'"

[brandond]

That's interesting - either should be fine: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#meaning-of-memory

[rancher-max]

Yeah it was really the 'B' that was breaking it. Setting it with Mi works fine as well as it can be parsed by the given regex. The upstream docs can be a little confusing due to statements like this:

... Each Container has a limit of 0.5 cpu and 128MiB of memory ...

But overall it's pretty clear there what to use, just making this update for users who don't want to go look upstream.

[brandond]

You're right, that's probably worth opening an issue in the upstream docs. They shouldn't use units in the text that the thing they're documenting doesn't support.