EOL Upgrades
Moves every repository in a migration off an end-of-life runtime, toolchain or base image. Pilots the upgrade on one repository per language first, then rolls out tier by tier once approved.
How it works
- Runs when: a migration is launched, or an end-of-life date for something production runs is close.
- Counts from production: reads the image each service actually runs. A merged pull request is not done until its image is running.
- Pilots first: one repository per language, never a tier-1 service. Each red pilot is fixed on its branch and the fix is added to the migration playbook.
- Rolls out with approval: tier by tier after the platform lead approves, with pilot results attached to every pull request. A repository blocked by a dependency gets a ticket on that dependency's owner.
- You get: every repository in exactly one state: running, merged but not running, in review, queued or blocked, with tier, owner, pull request and CI.
What it needs
- GitHub: read repositories, open pull requests
- Jira: read the migration epic, file blockers
- Kubernetes: read running images
- Slack (optional): post progress