linkerd check hangs if identity is unavailable
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
If using the `edge-19.4.1` Linkerd CLI with an older Linkerd installed such as `edge-19.3.2` which does not include the `linkerd-identity` deployment, `linkerd check` will hang forever waiting for `linkerd-identity` pods to become ready. This also prevents the use of other commands such as `linkerd dashboard`.
## Steps to reproduce:
1. Install Linkerd `edge-19.3.2` to a cluster
2. Use `edge-19.4.1` CLI to run `linkerd check`
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the mismatch by installing Linkerd edge-19.3.2 and running the edge-19.4.1 CLI commands `linkerd check` and `linkerd dashboard`. Trace how the check handles the missing `linkerd-identity` deployment; done means it reports the unavailable identity instead of hanging and does not block other commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100