Sidecar should have a livenessProbe per default #661
Labels
reliability
Protections against unsafe behavior, blockers go reconciliation, or other reliability concerns
Milestone
Currently the sidecar only has a
readinessProbe
to check if the Python process already has started up we should additionally add alivenessProbe
so that the container get's restarted when the Python process hangs. We've seen a few Python processes in the Sidecar that have stopped working and killing the process resolves the issue. With alivenessProbe
we don't have to manually kill the process. For thelivenessProbe
I would propose a defaultperiodSeconds
of30s
and afailureThreshold
of 2 which means after 2 minutes the container will be killed if not responding. We should add a field to enable this in the cluster spec and once we move to1.0.0
we will make this the default.The text was updated successfully, but these errors were encountered: