Health probs

[markelog]

Might be a good idea to consider adding route probs, like so -

1. https://blog.gopheracademy.com/advent-2017/kubernetes-ready-service/
2. https://blog.gopheracademy.com/advent-2017/kubernetes-ready-service/ (Step 9).

I.e. /readyz & healthz maybe more. Or like /ping or something :)

Even in the environments without kuber in it, they sometimes named like that. And we can add another integration test which actually connects to database.

Could be fun :)

[oleg-koval]

@markelog
Do you mean creating smth like "status" endpoint?

[markelog]

Yeah! Like in https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/#define-readiness-probes

Sometimes, applications are temporarily unable to serve traffic. For example, an application might need to load large data or configuration files during startup. In such cases, you don’t want to kill the application, but you don’t want to send it requests either. Kubernetes provides readiness probes to detect and mitigate these situations. A pod with containers reporting that they are not ready does not receive traffic through Kubernetes Services.

That's for readyz and health just checks if app is started or yeah status :). Something or other

[oleg-koval]

so we need to have:

• endpoint GET /status
• call from the container to GET /status

@markelog do you have an idea about the second one?

[markelog]

Second one might just do mongoose.connection.readyState and check if app has a connection with db... and that's should be it

[oleg-koval]

.

[markelog]

.!