:recycle: make deployment mechanism cleaner and working

[georgettica]

trafficstars

so far the docker-compose is the de-facto way to deploy monocle

this issue will track deploying with k8s from the current state until we can bring up the whole service

Acceptance criteria:

• start with the most independent service and deploy it (will be done in a task)
• work the way up until all of the services are deployed successfully

Template for service task:

• service name

• expected issues

• possible dependencies

• add docs && diagram for service to make it clear for the user how it works and how things are interconnected

• [x] elasticsearch

• [x] api

• [x] web

• [x] crawler

• [x] legacy-crawler

[georgettica]

@lioramilbaum please review whenever you see fit

[georgettica]

please assign to me

[georgettica]

after a while, I came back to this and I have some things I will tackle.. so spawning issues from the main one

[georgettica]

currently, without changes, the elasticsearch component spins up without an issue

[georgettica]

for the api, an issue has PR fix has been filed to make it deploy on k8s correctly with the current config. the issue is now on the component returning 404 for liveness https://github.com/change-metrics/monocle/pull/692

[georgettica]

the reason the api is blocking as seen in dependency graph here https://github.com/change-metrics/monocle/issues/690#issuecomment-953291765 after the elasticsearch which is working, the api is the next in the chain. and all the other services depend on it

[georgettica]

@lmilbaum so now we have most of the things done and we are waiting on small fixes

[georgettica]

All deoyment folder is complete, please let me know we can collaborate on #718 @TristanCacqueray @morucci