-
Notifications
You must be signed in to change notification settings - Fork 578
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
🌱 Remove invalid EKS test #5239
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test pull-cluster-api-provider-aws-e2e-eks Lets see if the overall EKS test suite passes now. |
/test pull-cluster-api-provider-aws-e2e-eks |
/test pull-cluster-api-provider-aws-e2e-eks |
While it may have worked in the past, CoreDNS no longer installs when there is just an EKS control plane. A user must also create a nodegroup for CoreDNS pods to be scheduled. Signed-off-by: Nolan Brubaker <[email protected]>
/test pull-cluster-api-provider-aws-e2e-eks |
I believe the EKS failures are unrelated, have been trying to address them with #5239 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
since the test only creates a control plane without worker nodes
/test pull-cluster-api-provider-aws-e2e-eks |
It's annoying that AWS has changed the behaviour. The tests are failing because of this check: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/main/test/e2e/suites/managed/eks_test.go#L54 It could be worth adding Or short term just remove the check. |
@nrb: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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-sigs/prow repository. I understand the commands that are listed here. |
EKS no longer allows CoreDNS to run when only a control plane exists; there are no schedulable nodes in this scenario, since users do not have access to control plane nodes.
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
The test for an EKS cluster only with a control plane and the CoreDNS addon no longer passes. This appears to be due to EKS's architecture - the control plane nodes are explicitly not available to user-managed deployments. It appears to have coincidentally worked in the past, but is no longer valid.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #5237
Special notes for your reviewer:
Checklist:
Release note: