New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e2e services wait for endpoint and endpoint slices #93829
Conversation
[sig-cli] Kubectl client Kubectl client-side validation should create/apply a CR with unknown fields for CRD with no validation schema expand_less | 1m16s test/e2e/kubectl/kubectl.go:1004 Aug 9 10:57:43.854: failed to create CR {"kind":"E2e-test-kubectl-2128-crd","apiVersion":"kubectl.example.com/v1","metadata":{"name":"test-cr"},"a":{"b":[{"c":"d"}]}} in namespace --namespace=kubectl-8200: error running /home/prow/go/src/k8s.io/kubernetes/bazel-bin/cmd/kubectl/linux_amd64_pure_stripped/kubectl --server=https://127.0.0.1:35115 --kubeconfig=/root/.kube/kind-test-config --namespace=kubectl-8200 create --validate=true -f -: Command stdout: stderr: Unable to connect to the server: context deadline exceeded (Client.Timeout exceeded while awaiting headers) error: exit status 1 |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/milestone v1.19
Since 1.19 endpoint slices is enabled by default, so all the e2e tests should consider them. The e2e networking tests for services use the jig object for all the tests, but was not taking into account endpoint slices. This considers endpoints slices for the method waitForAvailableEndpoint() Date: Sun Aug 9 12:34:06 2020 +0200
We can improve that further, but that's already net improvement. So let's make it. /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea, wojtek-t The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Since 1.19 endpoint slices is enabled by default, so all the e2e
tests should consider them.
Similar to #93597
I also found another test that need to be adapted
k8s.io/kubernetes/test/e2e/network/service_latency.go
kubernetes/test/e2e/network/service_latency.go
Line 295 in 62b8fae
/kind flake