chore(helm chart): cpu resources for server & objects increased (#1993)

specklesystems · Jan 25, 2024 · cf67a23 · cf67a23
1 parent 9aebb3f
commit cf67a23
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 8 deletions.
diff --git a/utils/helm/speckle-server/values.schema.json b/utils/helm/speckle-server/values.schema.json
@@ -814,7 +814,7 @@
             "cpu": {
               "type": "string",
               "description": "The CPU that should be available on a node when scheduling this pod.",
-              "default": "500m"
+              "default": "1000m"
             },
             "memory": {
               "type": "string",
@@ -829,7 +829,7 @@
             "cpu": {
               "type": "string",
               "description": "The maximum CPU that will be made available to the server Pod in a given period.",
-              "default": "1000m"
+              "default": "1500m"
             },
             "memory": {
               "type": "string",
@@ -1101,7 +1101,7 @@
             "cpu": {
               "type": "string",
               "description": "The CPU that should be available on a node when scheduling this pod.",
-              "default": "500m"
+              "default": "1000m"
             },
             "memory": {
               "type": "string",
@@ -1116,7 +1116,7 @@
             "cpu": {
               "type": "string",
               "description": "The maximum CPU that will be made available to the server Pod in a given period.",
-              "default": "1000m"
+              "default": "1500m"
             },
             "memory": {
               "type": "string",

diff --git a/utils/helm/speckle-server/values.yaml b/utils/helm/speckle-server/values.yaml
@@ -565,7 +565,7 @@ server:
     ## @param server.requests.cpu The CPU that should be available on a node when scheduling this pod.
     ## ref: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
     ##
-    cpu: 500m
+    cpu: 1000m
     ## @param server.requests.memory The Memory that should be available on a node when scheduling this pod.
     ## Depending on the Kubernetes cluster's configuration, exceeding this value may result in pod eviction from a node.
     ## ref: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
@@ -576,7 +576,7 @@ server:
     ## If this limit is exceeded, execution of the Pod will be paused until the next period.
     ## ref: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
     ##
-    cpu: 1000m
+    cpu: 1500m
     ## @param server.limits.memory The maximum Memory that will be made available to the server Pod.
     ## If this limit is exceeded, processes within the pod that request additional memory may be stopped.
     ## ref: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
@@ -718,7 +718,7 @@ objects:
     ## @param objects.requests.cpu The CPU that should be available on a node when scheduling this pod.
     ## ref: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
     ##
-    cpu: 500m
+    cpu: 1000m
     ## @param objects.requests.memory The Memory that should be available on a node when scheduling this pod.
     ## Depending on the Kubernetes cluster's configuration, exceeding this value may result in pod eviction from a node.
     ## ref: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
@@ -729,7 +729,7 @@ objects:
     ## If this limit is exceeded, execution of the Pod will be paused until the next period.
     ## ref: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/
     ##
-    cpu: 1000m
+    cpu: 1500m
     ## @param objects.limits.memory The maximum Memory that will be made available to the server Pod.
     ## If this limit is exceeded, processes within the pod that request additional memory may be stopped.
     ## ref: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/