As a Korifi user I want to see the app status as "crashed" when my app exits #3082
Assignees
Labels
bug
Something isn't working
Comments
This was referenced Jan 26, 2024
danail-branekov
added a commit
that referenced
this issue
Jan 26, 2024
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>
danail-branekov
added a commit
that referenced
this issue
Jan 26, 2024
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>
github-project-automation
bot
moved this from 🔄 In progress
to ✅ Done
in Korifi - Backlog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Acceptance
GIVEN I have pushed a crashing app
WHEN I get the app via
cf app my-appTHEN I eventually see the state of the app as
crashedThe text was updated successfully, but these errors were encountered: