Add request for cpu metric to support autoscaling

CS3219-AY2324S1 · Oct 24, 2023 · 09590ef · 09590ef
1 parent 7eb8c27
commit 09590ef
Show file tree

Hide file tree

Showing 7 changed files with 35 additions and 7 deletions.
diff --git a/deployment/gke-prod-manifests/admin-service-deployment.yaml b/deployment/gke-prod-manifests/admin-service-deployment.yaml
@@ -32,6 +32,10 @@ spec:
             - containerPort: 5005
               hostPort: 5005
               protocol: TCP
-          resources: {}
+          resources: 
+            # You must specify requests for CPU to autoscale
+            # based on CPU utilization
+            requests:
+              cpu: "250m"
       restartPolicy: Always
 status: {}
diff --git a/deployment/gke-prod-manifests/collaboration-service-deployment.yaml b/deployment/gke-prod-manifests/collaboration-service-deployment.yaml
@@ -47,6 +47,10 @@ spec:
             - containerPort: 5003
               hostPort: 5003
               protocol: TCP
-          resources: {}
+          resources: 
+            # You must specify requests for CPU to autoscale
+            # based on CPU utilization
+            requests:
+              cpu: "250m"
       restartPolicy: Always
 status: {}
diff --git a/deployment/gke-prod-manifests/frontend-deployment.yaml b/deployment/gke-prod-manifests/frontend-deployment.yaml
@@ -24,6 +24,10 @@ spec:
             - containerPort: 3000
               hostPort: 3000
               protocol: TCP
-          resources: {}
+          resources: 
+            # You must specify requests for CPU to autoscale
+            # based on CPU utilization
+            requests:
+              cpu: "250m"
       restartPolicy: Always
 status: {}
diff --git a/deployment/gke-prod-manifests/gateway-deployment.yaml b/deployment/gke-prod-manifests/gateway-deployment.yaml
@@ -34,6 +34,10 @@ spec:
             - containerPort: 4000
               hostPort: 4000
               protocol: TCP
-          resources: {}
+          resources: 
+            # You must specify requests for CPU to autoscale
+            # based on CPU utilization
+            requests:
+              cpu: "250m"
       restartPolicy: Always
 status: {}
diff --git a/deployment/gke-prod-manifests/matching-service-deployment.yaml b/deployment/gke-prod-manifests/matching-service-deployment.yaml
@@ -32,6 +32,10 @@ spec:
             - containerPort: 5002
               hostPort: 5002
               protocol: TCP
-          resources: {}
+          resources: 
+            # You must specify requests for CPU to autoscale
+            # based on CPU utilization
+            requests:
+              cpu: "250m"
       restartPolicy: Always
 status: {}
diff --git a/deployment/gke-prod-manifests/question-service-deployment.yaml b/deployment/gke-prod-manifests/question-service-deployment.yaml
@@ -32,6 +32,10 @@ spec:
             - containerPort: 5004
               hostPort: 5004
               protocol: TCP
-          resources: {}
+          resources: 
+            # You must specify requests for CPU to autoscale
+            # based on CPU utilization
+            requests:
+              cpu: "250m"
       restartPolicy: Always
 status: {}
diff --git a/deployment/gke-prod-manifests/user-service-deployment.yaml b/deployment/gke-prod-manifests/user-service-deployment.yaml
@@ -32,6 +32,10 @@ spec:
             - containerPort: 5001
               hostPort: 5001
               protocol: TCP
-          resources: {}
+          resources: 
+            # You must specify requests for CPU to autoscale
+            # based on CPU utilization
+            requests:
+              cpu: "250m"
       restartPolicy: Always
 status: {}