k8s/helm-based deployment of event pickup/index
Running docker-compose
service on na64-dev.cern.ch
host seemed to be tedious. I suspect there is a spurious memory leak of the event-reading process since the service seemed to be not really stable in a long-term perspective (yet, its hard to reproduce).
Currently, the deployment of services (db, event reader and RESTful API Flask-based backend with frontend) is performed by docker-compose run managed by ststemd service.
One have to reconsider this deployment model and probably change it in favor of kubernettes cluster. Benefits:
- Broken service will be healed up automatically
- We can dynamically scale up the back-end instances to handle indexing workload
- Management of services should be easier (we had few SELinux issues, AFAIR)