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

Changed default idle timeout and limit of running workspaces per user #14747

Merged
merged 1 commit into from
Oct 4, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ che.limits.workspace.env.ram=16gb
# length of time that the user has not interacted with the workspace, meaning that
# one of our agents has not received interaction. Leaving a browser window open
# counts toward idleness.
che.limits.workspace.idle.timeout=-1
che.limits.workspace.idle.timeout=1800000

##### USERS' WORKSPACE LIMITS #####

Expand All @@ -59,7 +59,7 @@ che.limits.user.workspaces.count=-1
# If the user has reached this threshold and they try to start an additional
# workspace, they will be prompted with an error message. The user will need to
# stop a running workspace to activate another.
che.limits.user.workspaces.run.count=-1
che.limits.user.workspaces.run.count=1

##### ORGANIZATIONS' WORKSPACE LIMITS #####

Expand Down
2 changes: 1 addition & 1 deletion deploy/kubernetes/helm/che/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ global:
cheWorkspaceServiceAccount: "che-workspace"
# If set, Che will bind the specified cluster role to the workspace service account when creating a workspace.
cheWorkspaceClusterRole: ""
workspaceIdleTimeout: "-1"
workspaceIdleTimeout: "1800000"
log:
loggerConfig: ""
appenderName: "plaintext"
Expand Down