resultsdb: Fix api pods running out of memory
This commit is contained in:
parent
8660a4d62f
commit
b513985390
1 changed files with 4 additions and 4 deletions
|
@ -94,13 +94,13 @@ spec:
|
||||||
httpGet:
|
httpGet:
|
||||||
path: /api/v2.0/
|
path: /api/v2.0/
|
||||||
port: 5001
|
port: 5001
|
||||||
# Limit to 384MB memory. This is probably *not* enough but it is
|
|
||||||
# necessary in the current environment to allow for 2 replicas and
|
|
||||||
# rolling updates, without hitting the (very aggressive) memory quota.
|
|
||||||
resources:
|
resources:
|
||||||
limits:
|
limits:
|
||||||
|
memory: 500Mi
|
||||||
|
cpu: 300m
|
||||||
|
requests:
|
||||||
memory: 384Mi
|
memory: 384Mi
|
||||||
cpu: 0.3
|
cpu: 300m
|
||||||
volumes:
|
volumes:
|
||||||
- name: config-volume
|
- name: config-volume
|
||||||
secret:
|
secret:
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue