Workaround to run Sonobuoy e2e tests on K8S cluster having node taints
I think there's a workaround for kubernetes versions prior to 1.17.
On kubernetes version v1.16 you can run Sonobuoy (Sonobuoy version v0.16.1 or higher) with providing the test framework flag: --allowed-not-ready-nodes=1
- then the test framework allows 1 node (your tainted node) to be "not-ready"
- this approach works fine for me with kubernetes v1.16.4 and Sonobuoy Version: v0.17.1
- see docs here: We have some nodes with custom taints in our cluster and the tests won't start. How can I run the tests?
- the Sonobuoy invocation looks like:
sonobuoy run --plugin-env=e2e.E2E_EXTRA_ARGS="--allowed-not-ready-nodes=1"And on kubernetes version prior to v1.16 it was more complicated. I haven't tested this but according to docs:
- you should also use the test framework flag:
--allowed-not-ready-nodes=1 - Before kubernetes v1.16, it was necessary to build your own custom image which could execute the tests with the desired options. See docs at: