[release-v3.25] Auto pick #7979: Typha tolerate #8066
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow typha deployment to tolerate the taint set via kubelet when used with --cloud-provider=external flag. We need typha to be able to schedule as soon as possible on new nodes since calico-node relies on it. Related Slack thread: https://calicousers.slack.com/archives/C0BCA117T/p1693469918340899
Co-authored-by: Lance Robson <lance@tigera.io>
coutinhop
added
release-note-required
✅ Deploy Preview for calico-v3-25 canceled.
|
lwr20
approved these changes
Sep 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry pick of #7979 on release-v3.25.
#7979: Typha tolerate
Original PR Body below
Description
Allow typha deployment to tolerate the taint set via kubelet when used with --cloud-provider=external flag. We need typha to be able to schedule as soon as possible on new nodes since calico-node relies on it.
Related issues/PRs
Related Slack thread:
https://calicousers.slack.com/archives/C0BCA117T/p1693469918340899
Todos
Someone should run the respective make target to generate manifests picking up this change.
Release Note