Sonobuoy must tolerate certain test taints #876
Labels
Milestone
Comments
johnSchnake
added a commit
that referenced
this issue
Sep 14, 2019
A new conformance test in v1.16 will add a taint to a node which can impact the sonobuoy aggregator pod as well as the e2e pod. This change adds the toleration to both the default job podspec and the aggregator. The default daemonset podspec already tolerates all taints. Fixes #876 Signed-off-by: John Schnake <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps did you take and what happened:
See kubernetes/kubernetes#82664 for some context; lots of conversations in slack.
TL;DR; we may allow some conformance tests to be also disruptive; specifically there are some w.r.t. taints that were causing evictions on a node and impacting sonobuoy. We need to tolerate these taints (or all taints?) in order to be sure that we do not get evicted during a test run.
What did you expect to happen:
Sonobuoy MUST be able to run all conformance tests (and, ideally, all of the e2e suite); not get evicted due to a taint added during a test.
Environment:
kubectl version): v1.16.0.beta.3The text was updated successfully, but these errors were encountered: