-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update troubleshooting guide to include new 2.4 checks #372
Labels
Comments
siggy
added a commit
to linkerd/linkerd2
that referenced
this issue
Jul 1, 2019
The `linkerd check` for healthy ReplicaSets had a generic `control plane components ready` description, and a hint anchor to `l5d-existence-psp`. While a ReplicaSet failure could definitely occur due to psp, that hintAnchor was already in use by the "control plane PodSecurityPolicies exist" check. Rename the `control plane components ready` check to `control plane replica sets are ready`, and the hintAnchor from `l5d-existence-psp` to `l5d-existence-replicasets`. Relates to linkerd/website#372. Signed-off-by: Andrew Seigner <siggy@buoyant.io>
siggy
added a commit
that referenced
this issue
Jul 1, 2019
Linkerd 2.4 introduces several new checks, as part of the `linkerd check` command: - `pre-l5d-existence` - `l5d-existence-mwc` - `l5d-existence-vwc` - `l5d-existence-psp` - `l5d-existence-linkerd-config` - `l5d-existence-replicasets` - `l5d-existence-unschedulable-pods` Depends on linkerd/linkerd2#3017 Fixes #372 Signed-off-by: Andrew Seigner <siggy@buoyant.io>
siggy
added a commit
to linkerd/linkerd2
that referenced
this issue
Jul 2, 2019
The `linkerd check` for healthy ReplicaSets had a generic `control plane components ready` description, and a hint anchor to `l5d-existence-psp`. While a ReplicaSet failure could definitely occur due to psp, that hintAnchor was already in use by the "control plane PodSecurityPolicies exist" check. Rename the `control plane components ready` check to `control plane replica sets are ready`, and the hintAnchor from `l5d-existence-psp` to `l5d-existence-replicasets`. Relates to linkerd/website#372. Signed-off-by: Andrew Seigner <siggy@buoyant.io>
siggy
added a commit
that referenced
this issue
Jul 2, 2019
Linkerd 2.4 introduces several new checks, as part of the `linkerd check` command: - `pre-l5d-existence` - `l5d-existence-mwc` - `l5d-existence-vwc` - `l5d-existence-psp` - `l5d-existence-linkerd-config` - `l5d-existence-replicasets` - `l5d-existence-unschedulable-pods` Depends on linkerd/linkerd2#3017 Fixes #372 Signed-off-by: Andrew Seigner <siggy@buoyant.io>
kleimkuhler
pushed a commit
that referenced
this issue
Jul 9, 2019
Linkerd 2.4 introduces several new checks, as part of the `linkerd check` command: - `pre-l5d-existence` - `l5d-existence-mwc` - `l5d-existence-vwc` - `l5d-existence-psp` - `l5d-existence-linkerd-config` - `l5d-existence-replicasets` - `l5d-existence-unschedulable-pods` Depends on linkerd/linkerd2#3017 Fixes #372 Signed-off-by: Andrew Seigner <siggy@buoyant.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Update the troubleshooting guide to include new checks introduced to the
linkerd check
command.Make sure the following hint anchors point to the correct docs:
pre-l5d-existence
l5d-existence-mwc
l5d-existence-vwc
l5d-existence-psp
l5d-existence-linkerd-config
l5d-linkerd-config-not-exists
l5d-existence-unschedulable-pods
Follow up of linkerd/linkerd2#2987 and linkerd/linkerd2#2510
The text was updated successfully, but these errors were encountered: