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.

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

As an admin, I would like to restrict the total number of 'Running' workspaces on a cluster #23081

Closed
ibuziuk opened this issue Aug 8, 2024 · 3 comments
Assignees
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/dashboard engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. good first issue Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you! kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/next

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Aug 8, 2024

Is your task related to a problem? Please describe

As an admin, I would like to restrict the total number of 'Running' workspaces on a cluster using CR property e.g.

 devEnvironments:
    maxNumberOfRunningWorkspaces: 200 // -1 by default which means unlimited

N.B. We already have maxNumberOfWorkspacesPerUser, but this issue is about limiting the overall number of the DW objects with the "Running" state on the cluster.

from the Dashboard UX perspective when the threshold is hit and yet another workspace is about to start the error message should be shown:

"Max number of workspaces running on the cluster: N"

Describe the solution you'd like

N/A

Describe alternatives you've considered

Additional context

N/A

@ibuziuk ibuziuk added kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. labels Aug 8, 2024
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 8, 2024
@ibuziuk ibuziuk added area/dashboard engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator labels Aug 8, 2024
@ibuziuk
Copy link
Member Author

ibuziuk commented Aug 8, 2024

@dkwon17 @AObuchow @tolusha @olexii4 @akurinnoy please, review
we need to prioritize it for the next sprint

@ibuziuk ibuziuk added sprint/next and removed sprint/next status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Aug 8, 2024
@ibuziuk ibuziuk changed the title As an admin, I would like to restrict the total number of 'Running' workspaces As an admin, I would like to restrict the total number of 'Running' workspaces on a cluster Aug 8, 2024
@ibuziuk ibuziuk added the good first issue Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you! label Aug 8, 2024
@tolusha
Copy link
Contributor

tolusha commented Aug 21, 2024

@ibuziuk
Does it sound better?
maxNumberOfRunningWorkspacesPerCluster

because we already have
maxNumberOfRunningWorkspacesPerUser

@ibuziuk
Copy link
Member Author

ibuziuk commented Aug 21, 2024

maxNumberOfRunningWorkspacesPerCluster sounds good

@tolusha tolusha closed this as completed Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/dashboard engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. good first issue Community, this issue looks easy to start with for a new contributor. Just take it. We'll help you! kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/next
Development

No branches or pull requests

3 participants