Switch backend mwapi-async calls from baremetal api_appserver cluster to kubernetes hosted mw-api-int-async
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| mw-page-content-change-enrich: Switch to mw-api-int-async | operations/deployment-charts | master | +2 -2 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T290536 Serve production traffic via Kubernetes | |||
| Resolved | Clement_Goubert | T333120 Migrate internal traffic to k8s | |||
| Resolved | Clement_Goubert | T357785 Migrate mw-page-content-change-enrich to mw-api-int |
Event Timeline
Comment Actions
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
Comment Actions
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?
Comment Actions
Change 1004156 merged by jenkins-bot:
[operations/deployment-charts@master] mw-page-content-change-enrich: Switch to mw-api-int-async
Comment Actions
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.
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2024-02-21T12:12:19Z] <claime> mw-page-content-change-enrich: Switch to mw-api-int-async - T357785
Comment Actions
I can confirm that mw-page-content-enrich now requests from mw-api-int (blue) and not the appserver cluster (yellow)
Marking resolved, thanks @BTullis