Introduce an API server & liveness endpoints (#13)
* wip
* Introduce an API server & liveness endpoints
Two things in this commit:
1- introduce an API Server which is used for liveness endpoint and for future api endpoint
2- implementation of a liveness endpoint for probing the scheduler internals
Why need a liveness ?
The liveness endpoint will try to send a schedule simulating a store event and it makes
sure that the event is triggered as expected, to check if there is no deadlock or an issue
in scheduler operation.
useful for kubernetes
Co-authored-by: fkarakas <[email protected]>
