A large part of these services' design is around their k8s-ness, which is absent in Beta Cluster, so we'll probably have to do something else (unless a k8s-on-Beta-Cluster option is going to be built?).
|Open||None||T261469 Launch demonstration system|
|Open||Krinkle||T261341 Performance review of Wikifunctions|
|In Progress||Jdforrester-WMF||T284162 Create a Beta Cluster version of Wikifunctions.org|
|Resolved||Jdforrester-WMF||T289315 Work out how we're going to have "production-like" versions of the wikifunctions evaluator and orchestrator services in Beta Cluster|
|Invalid||None||T295477 Request creation of deployment-prep-k8s VPS project|
OK, so my not-very-high-end plan is to have a Toolforge account, wikilambda-beta, in which an orchestrator and evaluator are continuously running and updated to HEAD, and which are pointed at by the default extension configuration. This way local developers, CI, and the Beta Cluster will all use these services 'out of the box'.