My pods sometimes appear that restarted automatically, but I don't have a liveness yet. I read that it can be the lifecycle of the pod that when you don't specify a RestartPolicy, by default is Always and when a Container crash, it restart automatically. But, I got confused because I thought that the liveness should do that. And as the lifecycle already do it, for what should I use the liveness probe? And as it is two different things, what is the difference between then?
What's the difference between Pod lifecycle and liveness?
162 views Asked by Arthur Ávila At
2
There are 2 answers
Related Questions in KUBERNETES
- php Variable name must change in for loop
- register_shutdown_function is not getting called
- Query returning zero rows despite entries existing
- Retrieving *number* pages by page id
- Automatically closing tags in form input?
- How to resize images with PHP PARSE SDK
- how to send email from localhost using codeigniter?
- Mariadb max Error while sending QUERY packet PID
- Multiusers login redirect different page in php
- Imaginary folder when I use "DirectoryIterator" in PHP?
Related Questions in LIVENESSPROBE
- php Variable name must change in for loop
- register_shutdown_function is not getting called
- Query returning zero rows despite entries existing
- Retrieving *number* pages by page id
- Automatically closing tags in form input?
- How to resize images with PHP PARSE SDK
- how to send email from localhost using codeigniter?
- Mariadb max Error while sending QUERY packet PID
- Multiusers login redirect different page in php
- Imaginary folder when I use "DirectoryIterator" in PHP?
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Popular Tags
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
If your app in the container crashes on its own, then k8s will restart it automatically. If you have a liveness probe, your POD may be restarted if the liveness probe fails. So in your situation, since you do not have a liveness probe, it is probably due to your app crashing.
Let's say your app is able to get in a state where it no longer executes requests, but it is not crashed (aka it is still up and running). This may happen if for example you have a deadlock in the code somewhere. In this case a liveness probe might be useful. The probe could test whether or not the app is in this deadlocked state. If so, the liveness probe would fail, and the POD restarted.
The difference is whether or not your app can go into a state where it is effectively down (not able to properly execute requests) while still remaining technically up (the PID in the container is still running). If your app can go into such a state, then I would say that a liveness probe is a good idea. It might also be a good idea if you do not know the answer to this question. If no harm can be done by having a liveness probe, then it might be a good idea. You'll just want to avoid restarting a perfectly fine POD if there is no problem.