fix: Add Fargate toleration to CoreDNS pods#56
Open
MElkady wants to merge 1 commit into
Open
Conversation
|
|
Member
|
I've added a question in the corresponding ticket. Please take a look as I'm unsure whether this PR will patch the underlying problem. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
CoreDNS pods carry the annotation
eks.amazonaws.com/compute-type: ec2by default, which prevents them from being scheduled on Fargate nodes. On a Fargate-only cluster this causes the "0/N nodes available: N node(s) had untolerated taint{eks.amazonaws.com/compute-type: fargate}" error.
The fix is to add a toleration for the Fargate taint so pods are accepted by Fargate nodes.
Fixes issue #47