-
Notifications
You must be signed in to change notification settings - Fork 70
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Consider a container crashed when in CrashLoopBackOff
Looking at the terminated state of a container is not reliable as this state does not last very long. Once a workload container exits (regardless of the exit code) consistently, k8s puts the container into `Waiting` state with reason `CrashLoopBackOff` until the scheduler starts it again. As this is an exponential backoff, this state tends to last longer and longer if the app keeps crashing. With the previous implementation of looking at the `Terminated` state we could never see the instance as `crashed` in the `cf app` output when we intentionally kept crashing it. Issue: #3082 Co-authored-by: Danail Branekov <danailster@gmail.com>
- Loading branch information
1 parent
bb3f7b6
commit 63ba385
Showing
3 changed files
with
42 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters