You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using this helm chart with jigasi support enabled, I noticed, that the container's readiness/liveness probes are simple tcp probes, instead of using the health check path provided by jigasi.
I would like to propose switching to using a http probe on port 8788, and path /about/health, at least for the liveness probes.
The advantages of this approach are:
The jigasi component would be able to automatically recover from failure without human intervention, in situations where connectivity to the underlying SIP gateway fails temporarily.
The text was updated successfully, but these errors were encountered:
Hello,
When using this helm chart with jigasi support enabled, I noticed, that the container's readiness/liveness probes are simple tcp probes, instead of using the health check path provided by jigasi.
I would like to propose switching to using a http probe on port
8788
, and path/about/health
, at least for the liveness probes.The advantages of this approach are:
The text was updated successfully, but these errors were encountered: