Description of problem:

While testing the changes for https://github.com/openshift/machine-config-operator/pull/3375, I am observing that the kubelet config isn't applying the system reserved values in bootstrap mode. 

I created a manifest folder and dropped following KubeletConfig

apiVersion: machineconfiguration.openshift.io/v1
kind: KubeletConfig
metadata:
  name: system-reserved-config2
spec:
  machineConfigPoolSelector:
    matchLabels:
      pools.operator.machineconfiguration.openshift.io/worker: ""
  kubeletConfig:
    systemReserved:
      cpu: 500m
      memory: 500Mi
      ephemeral-storage: 15Gi

However, the kubelet came up with 1Gi system reserved memory (instead of 500Mi as specified in the KubeletConfig above)

Version-Release number of selected component (if applicable):

How reproducible:

Always

Steps to Reproduce:

1. openshift-installer create manifests
2. drop the above KubeletConfig in that manifests folder
3. create the cluster

Actual results:

Kubelet came up with the system reserved memory value of 1Gi, which is a default value in absence of the user specified value. With the supplied KubeletConfig it should have come up with 500Mi system reserved memory.

 --system-reserved=cpu=500m,memory=1Gi,ephemeral-storage=1Gi

Expected results:

 --system-reserved=cpu=500m,memory=500Mi,ephemeral-storage=1Gi

Additional info:

Should we re-test the changes from https://github.com/openshift/machine-config-operator/pull/2547/ ?