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

Update aws-k8s-cni.yaml #776

Closed
wants to merge 1 commit into from
Closed

Update aws-k8s-cni.yaml #776

wants to merge 1 commit into from

Conversation

cheng0214
Copy link

Issue #, if available:
when i try to create kops cluster with vpc-cni network plugin, the master node has these taints, so
pod is not scheduled to master node.

Description of changes:
Add toleration to daemonset can fix this.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mogren mogren requested a review from jaypipes December 30, 2019 20:06
@mogren
Copy link
Contributor

mogren commented Dec 30, 2019

@cheng0214 By default, the CNI will tolerate any taint, see the official documentation:

An empty key with operator Exists matches all keys, values and effects which means this will tolerate everything.

That means the aws-node daemonset should schedule a pod on all nodes by default. For a related issue, see #508

@cheng0214
Copy link
Author

ok, I will close the PR. thanks you

@cheng0214 cheng0214 closed this Dec 31, 2019
@cheng0214 cheng0214 deleted the patch-1 branch April 27, 2020 14:06
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.

2 participants