-
Notifications
You must be signed in to change notification settings - Fork 558
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
Daemonset Antiaffinity for Fargate Nodes #329
Conversation
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Welcome @benmccown-amz! |
Hi @benmccown-amz. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Just got CLA sorted. |
/approve thank you, could you squash the commits into 1. e.g. git rebase -i upstream/master `` |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: benmccown-amz, wongma7 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/ok-to-test |
@wongma7 commits have been squashed. |
/lgtm thanks again |
/test pull-aws-efs-csi-driver-e2e |
1 similar comment
/test pull-aws-efs-csi-driver-e2e |
@wongma7 @ben-mccown
As per my understanding, above condition requires that the label "eks.amazonaws.com/compute-type" exists on the node for it to be evaluated. Now note that this label is only present on Fargate nodes, not on EC2 nodes beloging to a node group. This can be checked by running this command: The way I fixed it was changing the affinity to:
This way I ensure that the related pods are run on a node group and not Fargate. Last but not least, this affinity also has to be added to the "efs-csi-controller" Deployment element. Otherwise, the controller pods also throw errors. Hope this makes sense, kind regards. |
Is this a bug fix or adding new feature?
Bug fix. Relating to Issue 328
What is this PR about? / Why do we need it?
By default when following the docs at [1] with a mixed ec2/fargate EKS cluster the efs-csi-node DaemonSet will try to schedule to fargate nodes which results in pods becoming stuck in the "Pending" status.
This is easily resolvable with a node anti affinity rule.
[1] https://docs.aws.amazon.com/eks/latest/userguide/efs-csi.html
What testing is done?
I have tested the changes on my branch within a test cluster using the command below which is the exact command from the documentation but with a modified endpoint pointing to my test branch.