When a job is complete, the controller will indefinitely update its conditions
with a Complete condition. This change makes the controller exit the
reconcilation as soon as the job is already found to be marked as complete.

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Add 5-minute sleep in GKE for dead tunnels to be removed

Add kubernetes-test-go and ilk to source control.

Fix fake docker client to corretly report status of containers

Add a container runtime mock for testing

Revert "Remove FailedResourceType and return custom error"

Improve ES test resilience 

Add soak tests to source control.

Update docker-multinode instructions and version. Also run kube-proxy in a pod in the docker-multnode manifest

Changes required for test analyzer

Run test for grabbing metrics from Kubelet only on GCE

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Label 3 flaky deployment e2e tests with [Flaky]

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Fix data race by eliminating concurrency in test

Auto commit by PR queue bot

Auto commit by PR queue bot

Auto commit by PR queue bot

Kubelet doesn't perform checkpointing and loses all its internal states after
restarts. It'd then mistaken pods from the api server as new pods and attempt
to go through the admission process. This may result in pods being rejected
even though they are running on the node (e.g., out of disk situation). This
change adds a condition to check whether the pod was seen before and categorize
such pods as updates. The change also removes freeze/unfreeze mechanism used to
work around such cases, since it is no longer needed and it stopped working
correctly ever since we switched to incremental updates.

Label [Skipped] tests apprpriately