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.

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

[release-1.21] Reduce node startup time #4363

Merged
merged 3 commits into from
Oct 29, 2021

Conversation

brandond
Copy link
Member

Proposed Changes

  • If using the built-in CCM, wait for it to clear the uninitialized taint before starting the scheduler to ensure that pods can be scheduled immediately.
  • Optimize agent startup time by watching the local node instead of getting/sleeping in a loop.

Types of Changes

bugfix

Verification

See linked issue

Linked Issues

User-Facing Change

Resolved an issue that would occasionally cause K3s to take more than a minute to schedule initial pods on the first server in a cluster.

Further Comments

@brandond brandond requested a review from a team as a code owner October 29, 2021 22:47
Signed-off-by: Brad Davidson <[email protected]>
(cherry picked from commit 3fe460d)
Signed-off-by: Brad Davidson <[email protected]>
(cherry picked from commit 5acd0b9)
… err

Signed-off-by: Brad Davidson <[email protected]>
(cherry picked from commit 3da1bb3)
@brandond brandond merged commit 254d2f6 into k3s-io:release-1.21 Oct 29, 2021
@brandond brandond deleted the fix_4340_release-1.21 branch June 6, 2024 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants