Skip to content

Commit

Permalink
docs: update README
Browse files Browse the repository at this point in the history
  • Loading branch information
tyriis committed Mar 16, 2023
1 parent f3e3f51 commit 7e37006
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,14 @@ Get rid of `Pod was terminated in response to imminent node shutdown.` Pods fore

In kubernetes with gracefull shutdown enabled, pods can stay for long time perriods in a `broken` state. The state results in alerting getting fired by kube-prometheus-stack.

```console
[FIRING:1] Pod has been in a non-ready state for more than 15 minutes.
Severity: warning
Description: Pod default/some-container-7fb4c4fbc5-gbjwm has been in a non-ready state for longer than 15 minutes.
Details:
• alertname: KubePodNotReady • namespace: default • pod: some-container-7fb4c4fbc5-gbjwm • prometheus: observability/kube-prometheus-stack-prometheus • severity: warning
```

Most of the `solutions` on the internet describe an uncontrolled deletion of all Pods in `Error` or `Terminated` state.
Wich I consider as a bad idea, because you will not see anymore if real `Error` Pods are in your system.

Expand Down

0 comments on commit 7e37006

Please sign in to comment.