linkerd2/pkg/healthcheck
Dennis Adjei-Baah 20efe14fef
Fix issue where linkerd check would panic with replicationcontroller pod name in control plane (#2140)
When running Linkerd check with a control plane namespace that may contain an additional pod with a replication controller ID for pod names instead of a replicaSet ID, the check command panics because of an "index out of bounds" error.

This PR adds a check to make sure that, when parsing pod names during the `checkControllerRunning` healthcheck, we only check for linkerd control plane pods and that the pod name results in four or more substrings when split on '-'. This prevents the check from panicking when encountering a replication controller ID pod name.

Fixes #2084 

Signed-off-by: Dennis Adjei-Baah <dennis@buoyant.io>
2019-01-24 10:26:11 -08:00
..
healthcheck.go Fix issue where linkerd check would panic with replicationcontroller pod name in control plane (#2140) 2019-01-24 10:26:11 -08:00
healthcheck_test.go Fix issue where linkerd check would panic with replicationcontroller pod name in control plane (#2140) 2019-01-24 10:26:11 -08:00
sidecar.go When injecting, perform an uninject as a first step (#2089) 2019-01-17 10:15:23 -08:00
version.go Introduce version consistency checks (#2130) 2019-01-23 16:54:43 -08:00
version_test.go Introduce version consistency checks (#2130) 2019-01-23 16:54:43 -08:00