mirror of https://github.com/k3s-io/k3s
b3a1867529
Automatic merge from submit-queue (batch tested with PRs 55764, 55683, 55468, 54409, 55546). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Wait for server resources. For https://github.com/kubernetes/kubernetes/issues/55768. In e2e test for containerd, I sometimes see the following fail (e.g. https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-cri-containerd-e2e-gci-gce/178): ``` Nov 15 02:40:31.291: Couldn't delete ns: "e2e-tests-container-probe-dcvlw": unable to retrieve the complete list of server APIs: metrics.k8s.io/v1beta1: the server could not find the requested resource (&discovery.ErrGroupDiscoveryFailed{Groups:map[schema.GroupVersion]error{schema.GroupVersion{Group:"metrics.k8s.io", Version:"v1beta1"}:(*errors.StatusError)(0xc420bfd170)}}) ``` Usually, only the first few tests fail with this error. The error seems to be returned at this line https://github.com/kubernetes/kubernetes/blob/master/test/e2e/framework/util.go#L1170. @cheftako @caesarxuchao Does this change make sense to you? Or should I wait for something else to become ready? /cc @kubernetes/sig-api-machinery-pr-reviews **Release note**: ```release-note none ``` |
||
|---|---|---|
| .. | ||
| apimachinery | ||
| apps | ||
| auth | ||
| autoscaling | ||
| chaosmonkey | ||
| common | ||
| framework | ||
| generated | ||
| instrumentation | ||
| kubectl | ||
| lifecycle | ||
| manifest | ||
| multicluster | ||
| network | ||
| node | ||
| perftype | ||
| scalability | ||
| scheduling | ||
| servicecatalog | ||
| storage | ||
| testing-manifests | ||
| ui | ||
| upgrades | ||
| BUILD | ||
| README.md | ||
| e2e-example-config.json | ||
| e2e.go | ||
| e2e_test.go | ||
| examples.go | ||
| gke_local_ssd.go | ||
| gke_node_pools.go | ||
README.md
See e2e-tests