Use longer pod start timeouts for specific tests

The kubelet test here is using a one minute timeout, instead of the
normal framework.PodStartTimeout.

The DNS results validation functions pull several images including
the jessie-dnsutils which is a bit bigger than usual.

Author: johnbelamaric

test/e2e/common/kubelet.go

@@ -121,7 +121,7 @@ var _ = framework.KubeDescribe("Kubelet", func() {
 					return fmt.Errorf("expected non-zero exitCode and non-empty terminated state reason. Got exitCode: %+v and terminated state reason: %+v", contTerminatedState.ExitCode, contTerminatedState.Reason)
 				}
 				return nil
-			}, time.Minute, time.Second*4).Should(gomega.BeNil())
+			}, framework.PodStartTimeout, time.Second*4).Should(gomega.BeNil())
 		})
 
 		/*

test/e2e/network/dns_common.go

@@ -568,7 +568,7 @@ func validateDNSResults(f *framework.Framework, pod *v1.Pod, fileNames []string)
 		framework.Failf("ginkgo.Failed to create pod %s/%s: %v", pod.Namespace, pod.Name, err)
 	}
 
-	framework.ExpectNoError(f.WaitForPodRunning(pod.Name))
+	framework.ExpectNoError(f.WaitForPodRunningSlow(pod.Name))
 
 	ginkgo.By("retrieving the pod")
 	pod, err := podClient.Get(pod.Name, metav1.GetOptions{})
@@ -596,7 +596,7 @@ func validateTargetedProbeOutput(f *framework.Framework, pod *v1.Pod, fileNames
 		framework.Failf("ginkgo.Failed to create pod %s/%s: %v", pod.Namespace, pod.Name, err)
 	}
 
-	framework.ExpectNoError(f.WaitForPodRunning(pod.Name))
+	framework.ExpectNoError(f.WaitForPodRunningSlow(pod.Name))
 
 	ginkgo.By("retrieving the pod")
 	pod, err := podClient.Get(pod.Name, metav1.GetOptions{})