Sonobuoy is skipping all disruptive tests in spite of having the "--mode=certified-conformance" mode set.

From the results tar generated, you can see(under ./plugins/e2e/definition.json) it took the right mode(E2E_SKIP value is empty so that all tests run)

{"Definition":{"sonobuoy-config":{"driver":"Job","plugin-name":"e2e","result-format":"junit"},"spec":{"name":"e2e","image":"gcr.io/google-containers/conformance:v1.15.10","command":["/run_e2e.sh"],"env":[{"name":"E2E_FOCUS","value":"\\[Conformance\\]"},{"name":"E2E_SKIP"},{"name":"E2E_PARALLEL","value":"1"},{"name":"E2E_USE_GO_RUNNER","value":"true"}],"resources":{},"volumeMounts":[{"name":"results","mountPath":"/tmp/results"}],"imagePullPolicy":"Always"}},"SessionID":"41e34811cb054f13","Namespace":"sonobuoy","SonobuoyImage":"sonobuoy/sonobuoy:v0.16.5","CleanedUp":true,"ImagePullPolicy":"IfNotPresent","ImagePullSecrets":"","CustomAnnotations":null}

but the very first line in ./plugins/e2e/results/global/e2e.log tells me it skipped the disruptive ones

I0307 06:46:27.648927      19 test_context.go:406] Using a temporary kubeconfig file from in-cluster config : /tmp/kubeconfig-445061222
I0307 06:46:27.648999      19 e2e.go:243] Starting e2e run "cee5481b-8907-4d2d-a526-479ded6884e7" on Ginkgo node 1
Running Suite: Kubernetes e2e suite
===================================
Random Seed: 1583563586 - Will randomize all specs
Will run 215 of 4412 specs

I have followed general instructions to run this:

./sonobuoy --kubeconfig <path_to_my_kubeconfig> run --mode=certified-conformance

Am I missing something?