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

Make ws-daemon workspace class aware #10981

Closed
Tracked by #8261
Furisto opened this issue Jun 28, 2022 · 0 comments · Fixed by #11374
Closed
Tracked by #8261

Make ws-daemon workspace class aware #10981

Furisto opened this issue Jun 28, 2022 · 0 comments · Fixed by #11374
Assignees
@Furisto
Labels
team: workspace Issue belongs to the Workspace team

Comments

@Furisto
Copy link
Member

Furisto commented Jun 28, 2022 •
edited
Loading

Is your feature request related to a problem? Please describe

Support #8261

Describe the behaviour you'd like

ws-daemon needs to be aware of the workspace class of the workspace that it is limiting, so that it can apply the proper resource restrictions for that class.

Describe alternatives you've considered

n.a.

Additional context

Affected components:

  • ws-daemon
@Furisto Furisto mentioned this issue Jun 28, 2022
Closed
11 tasks
@jenting jenting added the team: workspace Issue belongs to the Workspace team label Jun 30, 2022
@Furisto Furisto moved this to In Progress in 🌌 Workspace Team Jul 13, 2022
@Furisto Furisto self-assigned this Jul 13, 2022
@Furisto Furisto mentioned this issue Jul 18, 2022
Merged
1 task
@Furisto Furisto moved this from In Progress to Backlog in 🌌 Workspace Team Aug 1, 2022
Repository owner moved this from Breakdown to Awaiting Deployment in 🌌 Workspace Team Aug 5, 2022
@kylos101 kylos101 moved this from Awaiting Deployment to In Validation in 🌌 Workspace Team Aug 15, 2022
@Furisto Furisto moved this from In Validation to Done in 🌌 Workspace Team Sep 12, 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

Successfully merging a pull request may close this issue.

Limit resources based on workspace class gitpod-io/gitpod
2 participants
@Furisto @jenting