Description: Service to generate geometric shapes from OSM PostgreSQL data and WDQS queries
Timeline: Q4
Diagram: [[ https://github.com/wikimedia/mediawiki-services-kartotherian/blob/master/docs/diagrams/output/geoshapesRequestDataFlow.png | Data flow diagram ]], [[ https://github.com/wikimedia/mediawiki-services-kartotherian/blob/master/docs/diagrams/output/backend.png | Maps backend diagram ]], and [[ https://github.com/wikimedia/mediawiki-services-kartotherian/blob/master/docs/diagrams/output/deploymentDiagram.png | Maps deployment diagram ]]
Technologies: nodejs
Point person: @MSantos
==== Background
As part of {T263854} work, geoshapes service will be extracted as a standalone service.
The service currently runs on bare-metal in `maps20xx.codfw.wmnet` and `maps10xx.eqiad.wmnet` and geoshapes access the PostgreSQL DB available in it
==== Acceptance Criteria
- [x] Extract geoshapes into it's own service/repo
- [x] Enable PG connections from k8s cluster to maps clusters
- [] Enabling the deployment-pipeline to generate the OCI (docker) container
- [] Creating the helm chart itself in deployment-charts
- [] Benchmark in a local env (if possible, don't go overboard we want coarse data, we 'll anyway have to finetune in real traffic)
- [] Submit the helmfile.d/services stanzas for review and get them merged
- [] Creation of k8s namespaces/token (SRE side, open up a task and we will get it done)
- [] Do the actual deployment
- [] Set up LVS, DNS and discovery (that's strictly on SRE side)
- [] Set up the traffic layer to send traffic to the service
- [] Acceptance tests
- [] Set up grafana dashboards