Currently, postgresql+postgis is implemented on bare metal, with each maps application server hosting its own postgres replica. Once kartotherian is fully containerized, this deployment won't make sense any more, and postgres should be moved into a dedicated cluster behind a read-write and a read-only, load-balanced discovery URL.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T198901 Migrate production services to kubernetes using the pipeline | |||
| Open | None | T321959 Tech Wishes - Maps service infrastructure deprecations | |||
| Open | None | T216826 Move Kartotherian to Kubernetes | |||
| Open | None | T322647 Create a dedicated postgresql+postgis cluster for maps |
Event Timeline
Comment Actions
@awight, on Tegola (which is running on k8s), we already have envoy doing load-balancing there, details can be found at tegola-vector-tiles. It makes sense to use the same solution for kartotherian I reckon, do you agree?