Page MenuHomePhabricator

wdqs v2: deploy wdqs-next
Closed, ResolvedPublic

Description

As a platform engineer operating wdqs v2, I would like a staging version of the service available in wdqs-next to test deployments before rolling out to production.

The building blocks are in place, we need to make sure we have the appriorate resource allocation in respective helmfiles.

In wdqs-next we won't need internal and external releases, and need only to target the main / scholarly split.

AC

  • a main release is available in wdqs-next
  • a scholarly release is avaialble in wdqs-next

Needs decision

  • Can these deployment replaced the eqiad test infra?

Details

Related Objects

StatusSubtypeAssignedTask
Opengmodena
Resolvedtrueg

Event Timeline

trueg changed the task status from Open to In Progress.Jul 21 2026, 8:34 AM
trueg claimed this task.
trueg moved this task from Incoming to Sprint 07 (2026/07/07 on the Wikidata Platform Team board.

Change #1313858 had a related patch set uploaded (by Trueg; author: Trueg):

[operations/deployment-charts@master] WDQSv2-next: Staging deployment of WDQSv2

https://gerrit.wikimedia.org/r/1313858

Both main-external and scholarly-external are running on eqiad on the test node:

NAME                                             READY   STATUS    RESTARTS   AGE   IP             NODE                                NOMINATED NODE   READINESS GATES
wdqs-main-external-backend-0                     3/3     Running   0          27m   10.67.29.107   dse-k8s-wdqs-test1001.eqiad.wmnet   <none>           <none>
wdqs-main-external-proxy-c59758598-qvcpn         2/2     Running   0          27m   10.67.28.148   dse-k8s-worker1024.eqiad.wmnet      <none>           <none>
wdqs-scholarly-external-backend-0                3/3     Running   0          27m   10.67.29.108   dse-k8s-wdqs-test1001.eqiad.wmnet   <none>           <none>
wdqs-scholarly-external-proxy-77b97fb9b7-hs588   2/2     Running   0          27m   10.67.31.4     dse-k8s-worker1018.eqiad.wmnet      <none>           <none>

This siffers slightly from wdqs where each release runs on a separate node (as of the time of this writing, this might change in the future).

Requests to the scholarly instance on wdqs-next work:

trueg@stat1008:~$ curl -i -XPOST -H"Content-Type:application/sparql-query" -d"select * where { ?s ?p ?o } limit 1" "https://wdqs2-next-scholarly-external.svc.eqiad.wmnet:30443/sparql"
HTTP/2 200 
content-length: 331
content-type: */*;charset=UTF-8
x-envoy-upstream-service-time: 90
date: Wed, 22 Jul 2026 10:36:19 GMT
server: istio-envoy

{"head":{"vars":["s","p","o"]},"results":{"bindings":[{"s":{"type":"uri","value":"http://www.wikidata.org/entity/Q100000547"},"p":{"type":"uri","value":"http://wikiba.se/ontology#identifiers"},"o":{"datatype":"http://www.w3.org/2001/XMLSchema#int","type":"literal","value":"0"}}]},"meta":{"query-time-ms":70,"result-size-total":1}}

Change #1313858 merged by jenkins-bot:

[operations/deployment-charts@master] WDQSv2-next: Staging deployment of WDQSv2

https://gerrit.wikimedia.org/r/1313858