linkerd2/multicluster
Alejandro Pedraza 571f505b6b
Move CP check after the readiness check (#5848)
* Move CP check after the readiness check

Moved the `can initialize client` and `can query the control plane API`
checks from the `linkerd-existence` section to the `linkerd-api` because
they required the `linkerd-controller` pod to not just be "Running" but
actually be ready.

This was causing `linkerd check` to show some port-forwarding warnings
when ran right after install.

This also allowed getting rid of the `CheckPublicAPIClientOrExit` function
and directly use `CheckPublicAPIClientOrRetryOrExit` (better naming
punted for later) which was refactored so it always runs the
`linkerd-api` checks before retrieving the client.

Other changes:

- Temporarily disabled `upgrade-edge` test because the latest edge has this readiness check issue
- Have the upgrade tests do proper pruning (stolen for @Pothulapati's #5673 😉 )
- Added missing label to tap SA (fixes #5850)
- Complete tap-injector Service selector
2021-03-01 19:47:25 -05:00
..
charts Remove linkerd prefix from extension resources (#5803) 2021-02-25 11:01:31 -05:00
cmd Move CP check after the readiness check (#5848) 2021-03-01 19:47:25 -05:00
service-mirror Revert "Rename multicluster annotation prefix and move when possible (#5771)" (#5813) 2021-02-24 12:54:52 -05:00
static extension: Separate multicluster chart and binary (#5293) 2020-12-04 16:36:10 -08:00
values Removed "do-not-edit" entries from values.yaml files (#5758) 2021-02-19 09:17:45 -05:00