• Kubernetes Submit Queue's avatar
    Merge pull request #37325 from ivan4th/fix-e2e-with-complete-pods-in-kube-system-ns · 4b44926f
    Kubernetes Submit Queue authored
    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'
    ```
    4b44926f
mesos.go 3.66 KB