-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[ws-daemon] Add support for limiting number of processes in workspaces #11448
Conversation
/werft run with-preview 👍 started the job as gitpod-build-aledbf-proc.1 |
Shouldn't the limit update when I update the configmap? The value stays the same, even after Kubernetes has replaced the configmap in the container filesystem. |
@Furisto please check you are using the latest build. I commit the fix for that not long ago. (also, keep in mind the update could take > 30s) Edit: if this does not work, we need to check the code that detects the changes in ws-daemon - not related to this PR) |
With the new build, the update behaves as expected. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, as @aledbf noted via Slack the preview environments don't yet use cgroups v2 so I can't directly verify but it looks sound to me.
Description
Allow setting a limit to the number of processes inside a workspace. By default, we have none.
How to test
"procLimit": 512
while true; do sleep 1 && date & done
bash: fork: retry: Resource temporarily unavailable
**
Release Notes
Werft options:
Note: testing this requires cgroups v2