Page MenuHomePhabricator

Migrate mw-page-content-change-enrich to mw-api-int
Closed, ResolvedPublic

Description

Switch backend mwapi-async calls from baremetal api_appserver cluster to kubernetes hosted mw-api-int-async

Event Timeline

Change 1004156 had a related patch set uploaded (by Clément Goubert; author: Clément Goubert):

[operations/deployment-charts@master] mw-page-content-change-enrich: Switch to mw-api-int-async

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

Clement_Goubert moved this task from Backlog to In Progress on the MW-on-K8s board.
Clement_Goubert moved this task from Incoming 🐫 to Doing 😎 on the serviceops board.

We're all set for this, according to wikitech some care needs to be taken for deployment, what exactly do we need to be aware of before going forward with it?

Change 1004156 merged by jenkins-bot:

[operations/deployment-charts@master] mw-page-content-change-enrich: Switch to mw-api-int-async

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

I'm happy for this change to go ahead. I'll keep an eye on the dashboard and be on the lookout for any alerts from this app.

Mentioned in SAL (#wikimedia-operations) [2024-02-21T12:12:19Z] <claime> mw-page-content-change-enrich: Switch to mw-api-int-async - T357785

I can confirm that mw-page-content-enrich now requests from mw-api-int (blue) and not the appserver cluster (yellow)

image.png (921×2 px, 127 KB)

Marking resolved, thanks @BTullis