linkerd2/controller
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
..
api Exclude telemetry generated by the control plane when requesting depl… (#493) 2018-03-05 17:58:08 -08:00
cmd Exclude telemetry generated by the control plane when requesting depl… (#493) 2018-03-05 17:58:08 -08:00
destination Fix flakey dns_test (#516) 2018-03-05 16:50:33 -08:00
gen Remove unused metrics (#322) 2018-02-09 17:14:17 -08:00
k8s Retry k8s watch endpoints on error (#510) 2018-03-07 13:40:43 -08:00
script Remove unused metrics (#322) 2018-02-09 17:14:17 -08:00
tap Ensure tap requests at least 1rps from each pod (#459) 2018-02-27 16:03:47 -08:00
telemetry Run go fix to fix context package imports (#470) 2018-02-28 13:25:33 -08:00
util Handle ExternalName-type svcs in destination service (#490) 2018-03-02 11:30:53 -08:00
Dockerfile Retry k8s watch endpoints on error (#510) 2018-03-07 13:40:43 -08:00