Changed default idle timeout and limit of running workspaces per user

eclipse-che · Oct 3, 2019 · 64f0805 · 64f0805
1 parent 8dac61e
commit 64f0805
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/multiuser.properties b/assembly/assembly-wsmaster-war/src/main/webapp/WEB-INF/classes/che/multiuser.properties
@@ -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                          #####
 
@@ -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                  #####
 

diff --git a/deploy/kubernetes/helm/che/values.yaml b/deploy/kubernetes/helm/che/values.yaml
@@ -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"