Skip to content

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

@ymmt2005

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions