From 915fd7db8a54bd222a85ddec56ea8e69969998ce Mon Sep 17 00:00:00 2001
From: Sebastian Kippe <sebastian@kip.pe>
Date: Mon, 4 Mar 2019 13:48:07 +0700
Subject: [PATCH] Add resource requests and limits for Gitea

Based on recent usage stats. If these are not set, the scheduler's
capacity check doesn't work and it will place new pods on nodes that are
actually not free enough for them.
---
 kubernetes/gitea-db.yaml     | 8 +++++++-
 kubernetes/gitea-server.yaml | 7 +++++++
 2 files changed, 14 insertions(+), 1 deletion(-)

diff --git a/kubernetes/gitea-db.yaml b/kubernetes/gitea-db.yaml
index 6b262cd..e66ed21 100644
--- a/kubernetes/gitea-db.yaml
+++ b/kubernetes/gitea-db.yaml
@@ -32,13 +32,19 @@ spec:
           value: gitea
         image: mariadb:10.3.10
         name: gitea-db
-        resources: {}
         ports:
           - containerPort: 3306
             name: mysql
         volumeMounts:
         - mountPath: /var/lib/mysql
           name: gitea-db-data
+        resources:
+          requests:
+            cpu: 250m
+            memory: 150Mi
+          limits:
+            cpu: 500m
+            memory: 300Mi
       restartPolicy: Always
       volumes:
       - name: gitea-db-data
diff --git a/kubernetes/gitea-server.yaml b/kubernetes/gitea-server.yaml
index 2709f9a..f2a035a 100644
--- a/kubernetes/gitea-server.yaml
+++ b/kubernetes/gitea-server.yaml
@@ -34,6 +34,13 @@ spec:
         volumeMounts:
         - mountPath: /data
           name: gitea-server-data
+        resources:
+          requests:
+            cpu: 250m
+            memory: 256Mi
+          limits:
+            cpu: 500m
+            memory: 512Mi
       restartPolicy: Always
       volumes:
       - name: gitea-server-data