Fixes flaky GKE kubectl test

This commit is contained in:
Sean Sullivan 2021-08-06 22:31:55 -07:00
parent dbebb8f2e8
commit 1ce594b7ee

View File

@ -644,6 +644,11 @@ var _ = SIGDescribe("Kubectl client", func() {
})
ginkgo.It("should handle in-cluster config", func() {
// This test does not work for dynamically linked kubectl binaries; only statically linked ones. The
// problem happens when the kubectl binary is copied to a pod in the cluster. For dynamically linked
// binaries, the necessary libraries are not also copied. For this reason, the test can not be
// guaranteed to work with GKE, which sometimes run tests using a dynamically linked kubectl.
e2eskipper.SkipIfProviderIs("gke")
// TODO: Find a way to download and copy the appropriate kubectl binary, or maybe a multi-arch kubectl image
// for now this only works on amd64
e2eskipper.SkipUnlessNodeOSArchIs("amd64")