Closed as not planned
Description
Currently all workspace application changes require the deployment of a new workspace cluster generation which hinders deployment frequency, infrastructure costs, and engineering speed.
We want to make it possible to do in-place upgrades for all workspace application-level roll-outs to mitigate those issues.
Value
- Enabling Gitpod Dedicated growth
- Increased deployment frequency
- Reduced engineering effort wasted on manual procedures
- Reduced infrastructure costs
Success Criteria
- Workspace application level roll-outs of multiple Gitpod installations are achievable with a click of button
- Roll-out success is automatically monitored, and in case of issues roll-back is automatically initiated
- Manual rollback should be similarly possible
- Roll-outs and roll-backs result in no service disruption
Dependencies
- [ws-manager] maintenance mode #15409
- Epic: Rewrite
ws-manager
as a Kubernetes controller #11416 - Dedicated support for in-place upgrades
- make registry-facade support in-place upgrades
- make ws-proxy support in-place upgrades
- remove gRPC calls from image-builder-mk3
Plan
TBD
Resources
Upgrading Gitpod in a Dedicated world - Gap analysis (internal)
FAQ
- Can we unlock any value before completing Epic: Rewrite
ws-manager
as a Kubernetes controller #11416?