Tim Hockin 64d4254217 Pods which have not "started" can not be "ready" ... Before this commit, containers which have both a `startupProbe` and a `readinessProbe` are marked as `ready=false` during stratup, but containers which have only a `startupProbe` are marked `ready=true`. This doesn't make sense. This commit only considers readiness if the container is considered to have "started", which leaves `ready=false` while starting up.		2020-06-16 21:34:51 -07:00
..
results	Add startupProbe result handling to kuberuntime	2019-11-13 08:12:54 +01:00
testing	Pass desiredPods to CleanupPods	2019-07-03 10:35:13 +08:00
BUILD	Run hack/update-vendor.sh	2020-05-16 07:54:33 -04:00
common_test.go	Removes container RefManager	2020-03-16 14:30:57 +01:00
OWNERS	Remove tallclair from some OWNERS files	2020-05-11 11:44:38 -07:00
prober_manager_test.go	switch over k/k to use klog v2	2020-05-16 07:54:27 -04:00
prober_manager.go	Pods which have not "started" can not be "ready"	2020-06-16 21:34:51 -07:00
prober_test.go	Removes container RefManager	2020-03-16 14:30:57 +01:00
prober.go	Merge pull request #85225 from DataDog/eric.mountain/cleanup_refmanager_master	2020-05-28 16:37:15 -07:00
worker_test.go	Removes container RefManager	2020-03-16 14:30:57 +01:00
worker.go	switch over k/k to use klog v2	2020-05-16 07:54:27 -04:00