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:
		
							parent
							
								
									cc6f31b4b9
								
							
						
					
					
						commit
						915fd7db8a
					
				| @ -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 | ||||
|  | ||||
| @ -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 | ||||
|  | ||||
		Reference in New Issue
	
	Block a user