Rob Scott 1ae53a15e6 Limiting the scope of new kubectl get e2e tests to decrease flakiness ...

The `kubectl get output` e2e test I'd previously added ended up being
flaky in certain e2e test scenarios. It relies on getting a list of API
resources in the cluster and running `kubectl get` calls against them.
The problem ended up being that other e2e tests could create resources
that would cause this test to fail. This change limits the scope of the
tests to not cover CRDs. This should still allow the test to catch new
Kubernetes resources with improperly configured kubectl output while
limiting the flakiness of the test.

2019-11-07 11:58:30 -08:00

107 KiB

Raw Blame History

View Raw