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
Currently all s6 services report only up or down but not if they are ready or not. It would be nice to know if the services are ready to receive traffic.
I'm writing a Kubernetes workload with an image based on this base image the service up status is great for startup and liveness probes but insufficient for readiness checks. Currently I'm checking like this /usr/bin/s6-svstat -o up /run/service/svc-kclient | grep --quiet true.
Proposed code change
I do know very little about kasm and s6 but am happy to volunteer my time. So I wanted to check first with the maintainers of this repo if a feature like this is feasible or even desirable.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is this a new feature request?
Wanted change
Currently all s6 services report only up or down but not if they are ready or not. It would be nice to know if the services are ready to receive traffic.
Here is the documentation I found regarding readiness checking: https://skarnet.org/software/s6/notifywhenup.html
Reason for change
I'm writing a Kubernetes workload with an image based on this base image the service up status is great for startup and liveness probes but insufficient for readiness checks. Currently I'm checking like this
/usr/bin/s6-svstat -o up /run/service/svc-kclient | grep --quiet true
.Proposed code change
I do know very little about kasm and s6 but am happy to volunteer my time. So I wanted to check first with the maintainers of this repo if a feature like this is feasible or even desirable.
The text was updated successfully, but these errors were encountered: