e75e28dcbf
* Set requests.memory=256MiB for the nginx-ingress-controller pod We decided to leave limits open as this will allow to support most of the generic use cases. * QoS from Guaranteed to Burstable This will make that application and ingress starve each other, both fighting for node resources for an optimal usage of CPU * Set priority class so that pods can take priority on a node that might have No CPU taint. task: 37625 story: 2006945 Change-Id: Ibc77ea64ad47f1a400d040f419f38bf52b9f0141 Signed-off-by: Diogo Guerra <diogo.filipe.tomas.guerra@cern.ch>
12 lines
377 B
YAML
12 lines
377 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
nginx-ingress-controller QoS changed from Guaranteed to Burstable.
|
|
Priority class 'system-cluster-critical' or higher for
|
|
nginx-ingress-controller.
|
|
fixes:
|
|
- |
|
|
nginx-ingress-controller requests.memory increased to 256MiB. This is a
|
|
result of tests that showed the pod getting oom killed by the node on
|
|
a relatively generic use case.
|