-
Notifications
You must be signed in to change notification settings - Fork 38.9k
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
e2e create pods only on schedulable nodes #101211
Conversation
We were avoiding the scheduled using the pod.Spec.NodeName directly, however, once we switched to using the node selector, the no_snat e2e test started to fail because was trying to schedule pods on nodes with taints, hence, failing the test.
@aojea: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea 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 |
/assign @wojtek-t @BenTheElder |
/lgtm |
/retest Review the full test history for this PR. Silence the bot with an |
We were avoiding the scheduler using the pod.Spec.NodeName directly,
however, once we switched to using the node selector, the no_snat
e2e test started to fail because was trying to schedule pods on
nodes with taints, hence, failing the test.
/kind failing-test
https://testgrid.k8s.io/sig-network-kind#sig-network-kind,%20IPv6,%20master