- Review and merge kartotherian helm chart
- Point to the staging Tegola
- Point to production maps postgresql, with read-only access
- Deploy kartotherian to k8s staging
- Configure the MediaWiki beta cluster to point to this staging container using $wgKartographerMapServer
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | akosiaris | T198901 Migrate production services to kubernetes using the pipeline | |||
| Resolved | None | T321959 Tech Wishes - Maps service infrastructure deprecations | |||
| Resolved | elukey | T216826 Move Kartotherian to Kubernetes | |||
| Open | None | T322522 Deploy containerized Kartotherian service to the beta cluster | |||
| Duplicate | None | T231006 Create helm chart for kartotherian k8s deployment | |||
| Resolved | None | T324471 Migrate our draft charts to newer scaffolding |
Event Timeline
Comment Actions
Kartotherian and Tegola now runs on Wikikube k8s, so we could create something like maps-beta.wikimedia.org as external endpoint, that the Beta cluster can point to.
The important bit is the datastore, since at the moment we don't have a dedicated staging postgres cluster. The kartotherian user should already be read-only for the prod cluster, but the risk is that somebody hammering maps-beta.wikimedia.org could affect the production traffic as well (kartotherian staging hammering the prod postgres cluster). This needs to be discussed with the Content Transform team.
@MSantos Adding you as FYI :)
Comment Actions
Could you elaborate on why we should work on k8s staging rather than a CloudVPS deployment-prep instance?
I would say that, considering Maps an under resourced project, it's good to have an option to empower volunteers to run the beta cluster if needed.
Comment Actions
@MSantos we already have a staging endpoint for Maps on K8s that we use to test new versions of Kartotherian, so it would be handy to just add an external endpoint and provide the same environment to the community for general Wikipedia/maps integration testing. The deployment-prep environment on cloud has been mostly abandoned for a long time, there is little effort in maintaining it and we'd need to come up with a different solution to spin up in there postgres, Tegola and Kartotherian, since I am pretty sure that the community will not have time to create the whole stack from scratch. They'd also need to spin up imposm for the new tiles etc..