Hm, I don't think the analytics systems interact too directly with MediaWiki.  They do use the EventStreamConfig extension's API from meta.wikimedia.org. The EventLogging extension is used to send instrumentation data, and is still used to host legacy EventLogging schemas.

I think for the most part, as long as those APIs keep working (mostly with meta.wikimedia.org), our stuff will work.  I'll let other folks chime in too.  You can follow up with us in IRC at #wikimedia-analytics, or in WMF Slack #data-engineering.

On Tue, Jun 21, 2022 at 4:25 AM Dominic Walden <dwalden@wikimedia.org> wrote:
Hello,

I am one of the test engineers on the QTE team.

There is a plan to migrate the MediaWiki software on production to
Kubernetes.

In preparation for this, we will be migrating test2wiki to Kubernetes
first so that QTE can test it and catch any bugs before the wider
roll-out.

I am trying to identify areas of our software for which the migration to
Kubernetes might pose a risk.

I wonder if this might be true of any of the software you are
responsible for. In particular, I am thinking about where MediaWiki is
interacting with different services in our ecosystem. I don't know
enough about this area to make an informed judgement.

Any ideas about what might be risky and in need of testing, and how one
might go about testing it on test2wiki
(https://test2.wikipedia.org/wiki/Main_Page) would be of great help to
me.

Let me know if you have any questions.

Thank you,

Dom
_______________________________________________
Analytics mailing list -- analytics@lists.wikimedia.org
To unsubscribe send an email to analytics-leave@lists.wikimedia.org