Skip to content

Epic: Enable in-place workspace application upgrades #15065

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 of 6 tasks
atduarte opened this issue Nov 30, 2022 · 3 comments
Closed
1 of 6 tasks

Epic: Enable in-place workspace application upgrades #15065

atduarte opened this issue Nov 30, 2022 · 3 comments
Labels
aspect: delivery meta: stale This issue/PR is stale and will be closed soon team: workspace Issue belongs to the Workspace team type: epic

Comments

@atduarte
Copy link
Contributor

atduarte commented Nov 30, 2022

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

  1. Enabling Gitpod Dedicated growth
  2. Increased deployment frequency
  3. Reduced engineering effort wasted on manual procedures
  4. Reduced infrastructure costs

Success Criteria

  1. Workspace application level roll-outs of multiple Gitpod installations are achievable with a click of button
  2. Roll-out success is automatically monitored, and in case of issues roll-back is automatically initiated
  3. Manual rollback should be similarly possible
  4. Roll-outs and roll-backs result in no service disruption

Dependencies

Plan

TBD

Resources

Upgrading Gitpod in a Dedicated world - Gap analysis (internal)

FAQ

  1. Can we unlock any value before completing Epic: Rewrite ws-manager as a Kubernetes controller #11416?
@kylos101
Copy link
Contributor

kylos101 commented Jan 1, 2023

👋 we are attempting a 🛹 in #15409, it'll let us try in-place upgrades for Gitpod Dedicated

@kylos101
Copy link
Contributor

kylos101 commented Jan 4, 2023

@corneliusludmann does the Scout Team plan to implement in-place upgrades for Workspace components in Gitpod Dedicated using our new #15444? I assume yes, that is in support of milestone 4 or milestone 5, but am unsure which milestone it is really being targeted for. For the meantime, Workspace team is beginning work on #11416, such that we may use it to achieve in-place upgrades for gitpod.io, too.

cc: @atduarte

@stale
Copy link

stale bot commented Sep 17, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Sep 17, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aspect: delivery meta: stale This issue/PR is stale and will be closed soon team: workspace Issue belongs to the Workspace team type: epic
Projects
No open projects
Status: No status
Development

No branches or pull requests

2 participants