Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Protect controller from becoming unschedulable #214

Merged
merged 3 commits into from
Jul 20, 2022
Merged

Protect controller from becoming unschedulable #214

merged 3 commits into from
Jul 20, 2022

Commits on Jul 13, 2022

  1. redesign the responsibilities of controller and agent 

    As part of prevent controller from becoming unschedualable, we redesign
the responsibilities of controler and agent. Basically new design makes
agent be able to complete a node update even lack controller's signal.
    @gthao313
    gthao313 committed Jul 13, 2022
    Configuration menu
    Copy the full SHA
    c2e314a View commit details
    Browse the repository at this point in the history

  2. update the node which hosts controller last 

    As part of Protect controller from becoming unschedulable, this part can
make brupop Update the node which hosts controller last. Therefore, this
approach can reduce the effect when controller pods is dead as much as possible.
    @gthao313
    gthao313 committed Jul 13, 2022
    Configuration menu
    Copy the full SHA
    1fdba8a View commit details
    Browse the repository at this point in the history

  3. make the controller a high-priority 

    As part of Protect controller from becoming unschedulable, this approach
means to give controller a high priority so that controller may be scheduled
sooner than Pods with lower priority if its scheduling requirements are met.
    @gthao313
    gthao313 committed Jul 13, 2022
    Configuration menu
    Copy the full SHA
    cb71fd3 View commit details
    Browse the repository at this point in the history