9 Commits (4ef423bfb1f7745ad52544131e0695eaba34bb2a)

Author	SHA1	Message	Date
Michael Taufen	73f2c55e0a	Bug fix: Use p.Name instead of pod.Name ... For example, if you used pod.GenerateName, pod.Name might be the empty string while p.Name contains the actual name of your pod. Thus passing pod.Name can result in a `resource name may not be empty` error.	2016-08-05 15:03:50 -07:00
Random-Liu	5c7ac701d3	Change TestContainerOutput to use the framework pod client.	2016-08-02 10:26:41 -07:00
Avesh Agarwal	f37d8fd60f	Fix node e2e (kubelet metrics) by adding GinkgoRecover to a goroutine ... to avoid panic	2016-07-20 13:26:56 -04:00
Random-Liu	fa8bd1d034	Change privileged test to use framework, so that all namespaces ... will be cleaned up by namespace controller.	2016-07-18 19:06:59 -07:00
Random-Liu	e40e82bd5c	Make it possible to share test between e2e and node e2e, ... and make container probing test shared to validate.	2016-07-18 14:05:08 -07:00
Michael Taufen	e709599854	Modify framework pod creation functions to return the server's representation of the pod ... Since PodInterface.Create returns the server's representation of the pod, which may differ from the api.Pod object passed to Create, we do the same from the framework's pod creation functions. This is useful if e.g. you create pods using Pod.GenerateName rather than Pod.Name, and you still want to refer to pods by name later on (e.g. for deletion).	2016-07-10 17:03:39 -07:00
Random-Liu	be8c7536ae	Add standard UpdatePod function in framework, and change ... the test to use it.	2016-07-06 11:04:34 -07:00
David McMahon	ef0c9f0c5b	Remove "All rights reserved" from all the headers.	2016-06-29 17:47:36 -07:00
Tim St. Clair	376b5f247a	Refactor common pod patterns to e2e framework.	2016-06-28 17:20:08 -07:00