Skip to content
This repository has been archived by the owner on Jul 7, 2020. It is now read-only.

gluster blockd status should be checked in liveness/readiness probe #394

Closed
raghavendra-talur opened this issue Nov 15, 2017 · 3 comments
Closed

Comments

@raghavendra-talur
Copy link
Member

raghavendra-talur commented Nov 15, 2017

Gluster container also has gluster-blockd service running. In some cases, user might want pod to fail readiness probe if gluster blockd is not running. This can be achieved by making a script as readiness checker which has checks in the following way

ret = 0
if glusterd not running
   ret = -1
if gluster-blockd not running AND ENV[blockd is must]==yes
   ret = -1
return ret
@jarrpa
Copy link
Contributor

jarrpa commented Nov 15, 2017

@raghavendra-talur Do you think we should do that in the pod spec or implement it as a script in the container?

@raghavendra-talur
Copy link
Member Author

@jarrpa script in the container. pod spec should only refer to the script.

@nixpanic
Copy link
Member

nixpanic commented Feb 5, 2019

This has been addressed through #523.

@nixpanic nixpanic closed this as completed Feb 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants