readiness + liveness for worker about contrib-helm-chart

[dabeck]

@grugnog due to a clustered environment we must always expect such failures. In my case the redis instance was shifted to another node and redash lost the connection without properly getting it back. The log stated in my initial comment was the last message of the workers.

[grugnog]

@dabeck good catch - were you able to identify why the connection was getting closed?
@arikfr do you know offhand if there is an easy way to monitor worker health? Kubernetes can support either a http endpoint (i.e. 200 status = OK) or a command (i.e. exit 0 = OK).
Alternatively perhaps a "crash on error" configuration setting that would cause services (both workers and main server even) to crash if they encounter any kind of error that is not recovering (perhaps after a few retries)?

[grugnog]

@dabeck are you still having this issue? Did you come up with any workaround?

[dabeck]

@grugnog I am currently no longer responsible for this issue. I'll let you know when I checked it in the next days/weeks.

[pparthesh]

add pgrep or ps to check running process inside pods.

[shubhwip]

pgrep and ps not available inside the worker's container.