Document and offer tips for common errors
@mateiidavid is already working on this.
Since Jun 24, 2021.
- Dominant language
- JavaScript
- Stars
- 60
- Forks
- 221
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 1
Description
Based on the Slack conversation [here](https://linkerd.slack.com/archives/C89RTCWJF/p1623159295132500), it might be worth to document (and explain) some of the more common errors that users might bump into.
One example (seen in the conversation linked above) is `HTTP Server service in fail-fast`, I've seen people ask questions about this one in particular a few times. We already have a [Troubleshooting page](https://linkerd.io/2.10/tasks/troubleshooting/) for warning messages and errors from `linkerd check`. This would be similar in scope but would cover issues that are more user facing and not necessarily tied to the installation of the control plane; explaining them and offering some debug tips might be helpful.
Thoughts?
I'll collect some of the common errors I have seen in this issue over the coming days.
#### Errors:
---
- [ ] `HTTP Server service in fail-fast`
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.
Assessment
This issue has not been assessed yet.