The /srv/status endpoint checks only the local process, not any dependencies. “Is the HTTP stack wedged?”, plus “am I in lame-duck?”. In Kubernetes terminology, this is the livenessProbe, not the readinessProbe.
If we want to introduce a readinessProbe, it should live at a different URL.
Probably Discourse.system_user.id instead of 1.