mirror of https://github.com/linkerd/linkerd2.git
e5b0ea28d4
## Motivation Testing #4167 has revealed some `linkerd check` failures that occur only because the checks happen too quickly after cluster creation or install. If retried, they pass on the second time. Some checkers already handle this with the `retryDeadline` field. If a checker does not set this field, there is no retry. ## Solution Add retries to the `l5d-existence-replicasets` `l5d-existence-unschedulable-pods` checks so that these checks do not fail during a chained cluster creation > install > check process. |
||
|---|---|---|
| .. | ||
| addr | ||
| admin | ||
| charts | ||
| config | ||
| filesonly | ||
| flags | ||
| healthcheck | ||
| identity | ||
| inject | ||
| issuercerts | ||
| k8s | ||
| profiles | ||
| prometheus | ||
| protohttp | ||
| smimetrics | ||
| tap | ||
| tls | ||
| trace | ||
| util | ||
| version | ||