test: Quarantine K8sServicesTest Check services across nodes

[twpayne]

This test has been unreliable for some time:

• CI: K8sServicesTest Checks fails with "Can not connect to service X from outside cluster" #12511
• CI: K8sServicesTest Checks service across nodes Tests NodePort BPF Tests with direct routing Tests LoadBalancer Connectivity to endpoint via LB #16399
• CI: K8sServicesTest Checks service across nodes Tests NodePort BPF Tests L2-less with Wireguard provisioned via kube-wireguarder Tests NodePort BPF #16971
• CI: K8sServicesTest Checks service across nodes Tests NodePort BPF Tests L2-less with Wireguard provisioned via kube-wireguarder Tests NodePort BPF #17176

[twpayne]

/test

[twpayne]

/ci-awscni

[twpayne]

/test

[pchaigno]

/test

[twpayne]

First Travis failure was due to hitting the Docker image pull rate limit (#17002).

Second Travis failure looks like #11560.

[pchaigno]

Given the test failures are unrelated and this PR is quarantining tests, could we proceed and merge it despite the failures? Otherwise we risk hitting a chicken and egg problem 😸

[twpayne]

Given the test failures are unrelated and this PR is quarantining tests, could we proceed and merge it despite the failures? Otherwise we risk hitting a chicken and egg problem 😸

Agreed :) Let's let the rest of the tests complete though to see what other flakes we get.

[pchaigno]

Given the test failures are unrelated and this PR is quarantining tests, could we proceed and merge it despite the failures? Otherwise we risk hitting a chicken and egg problem smile_cat

Agreed :) Let's let the rest of the tests complete though to see what other flakes we get.

They all finished already. The CI 3.0 tests won't start because you're PR only touches test/ so they are not affected.