mirror of https://github.com/k3s-io/k3s
4b44926f90
Automatic merge from submit-queue (batch tested with PRs 37325, 38313, 38141, 38321, 38333) Fix running e2e with 'Completed' kube-system pods As of now, e2e runner keeps waiting for pods in `kube-system` namespace to be "Running and Ready" if there are any pods in `Completed` state in that namespace. This for example happens after following [Kubernetes Hosted Installation](http://docs.projectcalico.org/v2.0/getting-started/kubernetes/installation/#kubernetes-hosted-installation) instructions for Calico, making it impossible to run conformance tests against the cluster. It's also to possible to reproduce the problem like that: ``` $ cat testjob.yaml apiVersion: batch/v1 kind: Job metadata: name: tst namespace: kube-system spec: template: metadata: name: tst spec: containers: - name: tst image: busybox command: ["echo", "test"] restartPolicy: Never $ kubectl create -f testjob.yaml $ go run hack/e2e.go -v --test --test_args='--ginkgo.focus=existing\s+RC' ``` |
||
|---|---|---|
| .. | ||
| BUILD | ||
| cleanup.go | ||
| exec_util.go | ||
| federation_util.go | ||
| framework.go | ||
| google_compute.go | ||
| kubelet_stats.go | ||
| log_size_monitoring.go | ||
| metrics_util.go | ||
| networking_utils.go | ||
| nodes_util.go | ||
| perf_util.go | ||
| pods.go | ||
| resource_usage_gatherer.go | ||
| test_context.go | ||
| util.go | ||