Health-Checks

All CDR Platform services have implemented health checks to communicate their state to Kubernetes.

If a pod enters an unhealthy state, Kubernetes will disable it and create a new one in its place.

Sync API and Async API

The API's are Kestral-hosted APIs which leverage HTTP health checks and will return a 200 OK when in a healthy state and a 503 when in an unhealthy state.

The checks can be made with a call to:

Markup

/api/health

Glasswall Engine and Cleanup

These services are not hosted with a web server, instead they spin up their own TCP listeners that accept inbound connections. As long as a connection occurs, a liveness probe will see that as being in the "healthy" state. If the service is in an unhealthy state the listener must be stopped.