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

Ability to set resource quotas per user #19767

Open
l0rd opened this issue May 7, 2021 · 9 comments
Open

Ability to set resource quotas per user #19767

l0rd opened this issue May 7, 2021 · 9 comments
Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months)

Comments

@l0rd
Copy link
Contributor

l0rd commented May 7, 2021 •
edited
Loading

Is your enhancement related to a problem? Please describe.

There is no way for an admin to limit the amount of memory/cpu/PV that a Che user is going to consume. That need to be done manually specifying the resources quotas at the namespace level.

Describe the solution you'd like

The CheCluster CR should have a some fields to specify users quotas for CPU/memory/PV
Che server should create resource quotas when it creates the user namespace.

Other solution

If the namespace already exist, has been created by the Che SA, and the quotas do not match, we should update the namespace quotas with the values that are in the CheCluster CR. That can be done at workspace startup or as soon as the CheCluster is updated.

Additional context

We should wait for #19717 before implementing this.
This is only applicable if a Che user correspond to Kubernetes user (for example if openshift OAuth or kubeproxy are used) and if the namespace strategy is per user <== we should deprecate other strategies anyway.

⚠️ This is not related to organizations/teams implementations
@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months) labels May 7, 2021
@l0rd l0rd mentioned this issue May 7, 2021
Closed
@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 May 7, 2021
@yhontyk yhontyk added area/che-server and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels May 7, 2021
@skabashnyuk
Copy link
Contributor

I think in the context of devworkspaces it's also related to #20219

@skabashnyuk skabashnyuk added area/devworkspace-operator engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. labels Aug 2, 2021
@l0rd l0rd changed the title Ability to set resource quotas per users Ability to set resource quotas per user Sep 6, 2021
@l0rd l0rd added area/che-server and removed engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. labels Feb 20, 2022
@che-bot
Copy link
Contributor

che-bot commented Aug 19, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 19, 2022
@l0rd
Copy link
Contributor Author

l0rd commented Aug 19, 2022

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 19, 2022
@che-bot
Copy link
Contributor

che-bot commented Feb 15, 2023

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 15, 2023
@l0rd
Copy link
Contributor Author

l0rd commented Feb 15, 2023

/remove-lifecycle stale

@l0rd l0rd removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 15, 2023
@che-bot
Copy link
Contributor

che-bot commented Aug 14, 2023

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 14, 2023
@l0rd
Copy link
Contributor Author

l0rd commented Aug 14, 2023

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 14, 2023
@che-bot
Copy link
Contributor

che-bot commented Feb 10, 2024

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 10, 2024
@l0rd
Copy link
Contributor Author

l0rd commented Feb 10, 2024

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/che-server kind/enhancement A feature request - must adhere to the feature request template. kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. roadmap/6-months Epics that are planned to complete in the medium term (within 6 months)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@l0rd @skabashnyuk @sleshchenko @yhontyk @che-bot