Skip to content
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

Liveness probe is not working #135

Closed
alewitt2 opened this issue Feb 18, 2021 · 1 comment
Closed

Liveness probe is not working #135

alewitt2 opened this issue Feb 18, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@alewitt2
Copy link
Member

our razeedeploy resources are getting into a bad state, and basically stalling out. What we expect to happen, is the liveness custom script will fail, and kubernetes will see that and restart the pod. we have seen the script works as expected, but kube isnt restarting the pod.

We either need to investigate if our script is not returning the correct error response, or look into setting up a new liveness check that kube will respect.

example liveness probe definition https://github.com/razee-io/RemoteResource/blob/master/kubernetes/RemoteResource/resource.yaml#L55-L58

example liveness script that should force kube to restart us on script failing https://github.com/razee-io/RemoteResource/blob/master/sh/liveness.sh#L18-L31

@alewitt2 alewitt2 added the bug Something isn't working label Feb 18, 2021
@alewitt2
Copy link
Member Author

  1. setup minikube or kubernetes on docker desktop setup.
  2. build docker image
    1. runs a shell script that touches file once
    2. sleeps 2hr
  3. put that docker image into a deployment yaml, with a liveness script defined
  4. run that deployment on your local test cluster and see if it works as we think it should

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants