-
Notifications
You must be signed in to change notification settings - Fork 539
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.
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
support liveness probe configure in kubernetes yaml #4482
Comments
Yes, it is indeed repetitive, there is no PR of #1096. Additionally, could consider using the https:/kubernetes-csi/livenessprobe project replace? |
Yes i have mentioned different options in #1096, considering it am closing this as duplicate, Thank you |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the feature you'd like to have
When the liveness check fails, the container should be restarted. Currently, the failure of the check can only be determined through the /metrics path with csi_liveness as shown below:
This is not very friendly for pod probe checks in Kubernetes. A common way to check pods is through the following method:
Could you provide an endpoint for liveness to facilitate probe checks?
What is the value to the end user? (why is it a priority?)
When a health check fails, the container can be restarted instead of showing as running but not being able to do anything.
How will we know we have a good solution? (acceptance criteria)
The text was updated successfully, but these errors were encountered: