As an event platform engineer, I need to understand how I would upgrade an application
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T317045 [Epic] Re-architect the Search Update Pipeline | |||
| Open | None | T340548 [EPIC] Deployment of the Search Update Pipeline on Flink / k8s | |||
| Open | lbowmaker | T328561 [Event Platform] Flink Operations | |||
| Resolved | gmodena | T328569 [Flink Operation] How to handle app upgrades |
Give how the flink k8s operator handles restarts, this task might end up being a subtask of https://phabricator.wikimedia.org/T328563.
The deployment and restart docs do already cover some bits of the application upgrade process: https://www.mediawiki.org/wiki/Platform_Engineering_Team/Event_Platform_Value_Stream/Pyflink_Enrichment_Service_Deployment
Should this ticket cover upgrades to other things as well (Flink, Python?)
I think those are orthogonal to application upgrades. Changing Flink and Python version would require changes to Flink's base docker images. It would follow the generic Gerrit CR process.