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.
This commit is contained in:
Basti 2019-03-04 13:48:07 +07:00
parent cc6f31b4b9
commit 915fd7db8a
No known key found for this signature in database
GPG Key ID: BE4634D632D39B67
2 changed files with 14 additions and 1 deletions

View File

@ -32,13 +32,19 @@ spec:
value: gitea value: gitea
image: mariadb:10.3.10 image: mariadb:10.3.10
name: gitea-db name: gitea-db
resources: {}
ports: ports:
- containerPort: 3306 - containerPort: 3306
name: mysql name: mysql
volumeMounts: volumeMounts:
- mountPath: /var/lib/mysql - mountPath: /var/lib/mysql
name: gitea-db-data name: gitea-db-data
resources:
requests:
cpu: 250m
memory: 150Mi
limits:
cpu: 500m
memory: 300Mi
restartPolicy: Always restartPolicy: Always
volumes: volumes:
- name: gitea-db-data - name: gitea-db-data

View File

@ -34,6 +34,13 @@ spec:
volumeMounts: volumeMounts:
- mountPath: /data - mountPath: /data
name: gitea-server-data name: gitea-server-data
resources:
requests:
cpu: 250m
memory: 256Mi
limits:
cpu: 500m
memory: 512Mi
restartPolicy: Always restartPolicy: Always
volumes: volumes:
- name: gitea-server-data - name: gitea-server-data