3 Commits

Author	SHA1	Message	Date
Dennis Adjei-Baah	ad42f2f8ab	Retry k8s watch endpoints on error (#510) ... Shortly after conduit is installed in k8s environment. The control plane component that establishes a watch endpoint with k8s run in to networking issues during proxy initialization. During failure, each watcher fails to retry its connection to k8s watch endpoint which leads to timeouts and eventually, multiple controller pod restarts. This PR adds retry logic to each "watch" enabled package. fixes #478 Signed-off-by: Dennis Adjei-Baah <dennis@buoyant.io>	2018-03-07 13:40:43 -08:00
Kevin Lingerfelt	e56be9bf0e	Bump k8s watch intialization timeout, cleanup logging (#166) ... Signed-off-by: Kevin Lingerfelt <kl@buoyant.io>	2018-01-17 15:31:01 -08:00
Kevin Lingerfelt	1dc1c00a2a	Upgrade k8s.io/client-go to v6.0.0 (#122) ... * Sort imports Signed-off-by: Kevin Lingerfelt <kl@buoyant.io> * Upgrade k8s.io/client-go to v6.0.0 Signed-off-by: Kevin Lingerfelt <kl@buoyant.io> * Make k8s store initialization blocking with timeout Signed-off-by: Kevin Lingerfelt <kl@buoyant.io>	2018-01-11 10:22:37 -08:00