5 Commits (347ce513cc599cbc2312ce9ea2e3e857e965989b)

Author	SHA1	Message	Date
Yu-Ju Hong	b906e34576	kubelet: trigger pod workers independently ... Currently, whenever there is any update, kubelet would force all pod workers to sync again, causing resource contention and hence performance degradation. This commit flips kubelet to use incremental updates (as opposed to snapshots). This allows us to know what pods have changed and send updates to those pod workers only. The `SyncPods` function has been replaced with individual handlers, each handling an operation (ADD, REMOVE, UPDATE). Pod workers are still triggered periodically, and kubelet performs periodic cleanup as well. This commit also spawns a new goroutine solely responsible for killing pods. This is necessary because pod killing could hold up the sync loop for indefinitely long amount of time now user can define the graceful termination period in the container spec.	2015-08-25 17:52:01 -07:00
Mike Danese	8e33cbfa28	rewrite go imports	2015-08-05 17:30:03 -07:00
Mike Danese	06c35a177c	unlink testlibs from kube-apiserver and kubelet	2015-06-23 12:04:05 -07:00
Prashanth Balasubramanian	b5ed0e9b13	Dont generatePodStatus twice for new pods	2015-06-11 17:18:16 -07:00
Yifan Gu	52af792852	kubelet: Fix racy kubelet tests. ... Add fakePodWorkders to run syncPod() in serial for testing.	2015-05-11 12:50:33 -07:00