Make kubelet and kube-proxy get started before kube-controller-manager and kube-scheduler

[ymmt2005]

What

Currently, kubelet and kube-proxy start after kube-controller-manager and kube-scheduler.
This could decrease the chances for Pods to be distributed among a large number of Nodes.

Reorder the operations so that Node resources get created before kube-scheduler and kube-controller-manager.

How

Describe how to address the issue.

Checklist

• Finish implentation of the issue
• Test all functions
• Have enough logs to trace activities
• Notify developers of necessary actions