As a second step towards moving production traffic to kubernetes, migrate test.wikidata.org to kubernetes.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| trafficserver: move testwikidata to kubernetes | operations/puppet | production | +9 -7 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| In Progress | None | T290536 Serve production traffic via Kubernetes | |||
| Resolved | Clement_Goubert | T331268 Migrate testwikidata to Kubernetes |
Event Timeline
Comment Actions
Change 894529 had a related patch set uploaded (by Clément Goubert; author: Clément Goubert):
[operations/puppet@production] trafficserver: move testwikidata to kubernetes
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2023-03-15T11:00:32Z] <claime> Redirecting test.wikidata.org to mw-on-k8s - T331268/25
Comment Actions
Change 894529 merged by Clément Goubert:
[operations/puppet@production] trafficserver: move testwikidata to kubernetes
Comment Actions
test.wikidata.org will now be progressively moved to mw-on-k8s as puppet runs happen.
Feel free to open subtasks for any issue that arises.
Comment Actions
FWIW, I tried running our browser test suite against Wikidata.
$ nvm use 14 $ node --version v14.19.1 $ MW_SERVER=https://test.wikidata.org MW_SCRIPT_PATH=/w MEDIAWIKI_USER='Lucas Werkmeister CI (WMDE)' MEDIAWIKI_PASSWORD='redacted' npm run selenium-test:repo
Plenty of tests failed, for benign reasons (e.g., the newly minted user couldn’t protect pages or block itself, and was subject to lower rate limits); we also don’t usually run these tests against Test Wikidata, and I don’t often run them locally at all. But several of the specs passed, and plenty of successful edits were made, so I’m counting that as a success.