How can I tell if workerd started its services?

[cp-20]

Background

I am curious about implementing FaaS using workerd on K8s. Since workerd cannot be configured dynamically (means its config cannot be changed without restarting), I would like to use rollout restarting. It is needed for the strategy to know if workerd is ready or not.

My current view

In my testing, services on workerd start a bit later than workerd itself starts, so I put a dummy service for startup probe. If we can get a healthy response from the service, workerd is regarded as healthy. It almost works but there are problems of the overhead and it is not 100% accurate.

Does anyone have other better idea?

[kentonv]

If workerd is accepting connections on the port you configured, then it is ready.

It almost works but there are problems of the overhead and it is not 100% accurate.

What do you mean here?

[cp-20]

I understand. Thanks!

It almost works but there are problems of the overhead and it is not 100% accurate.

What do you mean here?

This means rolling updates with config changes on K8s (K3s) will drop a few requests. I tested with this repo: https://github.com/cp-20/ns-workerd-test

This drop may be ignorable and should be caused by another problem...? Anyway, Thanks for your answer.