Skip to content
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.

Sign up for GitHub

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 KubeNodeNotReady.md #51

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update KubeNodeNotReady.md #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/runbooks/kubernetes/KubeNodeNotReady.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ weight: 20

KubeNodeNotReady alert is fired when a Kubernetes node is not in `Ready`
state for a certain period. In this case, the node is not able to host any new
pods as described [here][KubeNode].
pods as described [here](https://kubernetes.io/docs/concepts/architecture/nodes/#condition).

## Impact

Expand Down Expand Up @@ -41,5 +41,5 @@ API or kubelet).
Once, the problem was resolved that prevented node from being replaced,
the instance should be terminated.

See [KubeNode](https://kubernetes.io/docs/concepts/architecture/nodes/#condition)
See [node problem detector](https://github.com/kubernetes/node-problem-detector)
* See [KubeNode](https://kubernetes.io/docs/concepts/architecture/nodes/#condition)
* See [node problem detector](https://github.com/kubernetes/node-problem-detector)