Bootstrap MachineConfigController cannot start due to OOM in newly installed 4.13 cluster

Issue

• Bootstrap MachineConfigController cannot start due to OOM in newly installed 4.13 cluster
• The machine-config-controller Pod is killed continously. This is causing MachineConfigServer unable to start when bootstrapping

[  395.564698] Memory cgroup out of memory: Killed process 17368 (machine-config-) total-vm:6862808kB, anon-rss:36024kB, file-rss:43216kB, shmem-rss:0kB, UID:0 pgtables:1040kB oom_score_adj:999
[  396.774413] Memory cgroup out of memory: Killed process 17606 (machine-config-) total-vm:5314184kB, anon-rss:39648kB, file-rss:40696kB, shmem-rss:0kB, UID:0 pgtables:844kB oom_score_adj:999
[  410.870707] Memory cgroup out of memory: Killed process 18772 (machine-config-) total-vm:5971624kB, anon-rss:42680kB, file-rss:41300kB, shmem-rss:0kB, UID:0 pgtables:932kB oom_score_adj:999
[  442.227604] Memory cgroup out of memory: Killed process 20075 (machine-config-) total-vm:6490564kB, anon-rss:39412kB, file-rss:42708kB, shmem-rss:0kB, UID:0 pgtables:984kB oom_score_adj:999
[  484.963679] Memory cgroup out of memory: Killed process 20833 (machine-config-) total-vm:6710480kB, anon-rss:36772kB, file-rss:43152kB, shmem-rss:0kB, UID:0 pgtables:1016kB oom_score_adj:999

• This issue doesn't happen on 4.13.6