Page MenuHomePhabricator

Figure out if wikibase-registry should move to wbstack or maybe use k8s natively
Closed, DeclinedPublic

Description

Better than running docker-compose directly in a Cloud VPS VM, we should probably migrate it forward to a system more intended for production.

Possible options:

  • move it to wbstack
  • maybe make it use Kubernetes directly (with source-controlled config files, see T287586)

Somewhat related tasks:

Event Timeline

WBStack would be a convenient solution. Is there anything custom about the registry? Is anything unique to the current hosting relevant, like losing access to the WMF tile server for Kartographer - would this be avoided via Kubernetes?

(Kartographer is not currently installed, so maps can't be rendered in WDQS... in fact, it seems all queries linked on the front page seem to be breaking with 502 Bad Gateway, perhaps WDQS or the proxy needs restarting? If it too ran out of disk space, it may have had issues.)

in fact, it seems all queries linked on the front page seem to be breaking with 502 Bad Gateway.

😬

Thanks for pointing that out! I look into it - that's not how it is supposed to be

in fact, it seems all queries linked on the front page seem to be breaking with 502 Bad Gateway.

😬

Thanks for pointing that out! I look into it - that's not how it is supposed to be

Fixed now, after restarting several containers. Probably more fallout from the VM running out of space

Since this task was created I have set up a new Wikibase registry on Wikibase.Cloud. See T338960

Wikibase Registry has been closed in favor of https://wikibase.world hosted on Wikibase.Cloud.