Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support pvc workspace classes #11357

Closed
Tracked by #8261
Furisto opened this issue Jul 13, 2022 · 4 comments
Closed
Tracked by #8261

Support pvc workspace classes #11357

Furisto opened this issue Jul 13, 2022 · 4 comments
Assignees
@Furisto
Labels
team: workspace Issue belongs to the Workspace team

Comments

@Furisto
Copy link
Member

Furisto commented Jul 13, 2022 •
edited
Loading

Is your feature request related to a problem? Please describe

We need to test pvc for workspace backups without having impact on workspaces that are still doing backup with gcp object storage.

Describe the behaviour you'd like

Define an internal workspace classes that are only available to gitpodders, that ensure that workspaces are started with pvc and are scheduled to different nodes.
@Furisto Furisto added the team: workspace Issue belongs to the Workspace team label Jul 13, 2022
@Furisto Furisto moved this to Scheduled in 🌌 Workspace Team Jul 13, 2022
@Furisto Furisto mentioned this issue Jul 13, 2022
Closed
11 tasks
@Furisto Furisto moved this from Scheduled to In Progress in 🌌 Workspace Team Jul 23, 2022
@utam0k
Copy link
Contributor

utam0k commented Jul 26, 2022

Who is working on this issue? I think @Furisto?

@Furisto Furisto mentioned this issue Jul 26, 2022
Merged
1 task
@Furisto Furisto self-assigned this Jul 26, 2022
@Furisto Furisto moved this from In Progress to Backlog in 🌌 Workspace Team Aug 1, 2022
@kylos101
Copy link
Contributor

kylos101 commented Aug 5, 2022

@Furisto can you link the draft PRs to this issue? 🙏

@kylos101 kylos101 moved this from Breakdown to Scheduled in 🌌 Workspace Team Aug 8, 2022
@kylos101
Copy link
Contributor

@Furisto moving to in-progress, as you have two open PRs for this already 🙏

@kylos101 kylos101 moved this from Scheduled to In Progress in 🌌 Workspace Team Aug 11, 2022
@kylos101
Copy link
Contributor

@sagor999 for 👀

Repository owner moved this from In Progress to Awaiting Deployment in 🌌 Workspace Team Aug 16, 2022
@jenting jenting moved this from Awaiting Deployment to In Validation in 🌌 Workspace Team Aug 25, 2022
@Furisto Furisto moved this from In Validation to Done in 🌌 Workspace Team Aug 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Furisto Furisto

Labels
team: workspace Issue belongs to the Workspace team
Projects
No open projects
🌌 Workspace Team
Status: Done
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kylos101 @utam0k @sagor999 @Furisto