[
https://issues.apache.org/jira/browse/YUNIKORN-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-536.
--------------------------------------------
Fix Version/s: 0.10
Resolution: Fixed
Changes are committed and backported.
If this should be made configurable as part of the helm deployment then that
requires a new Jira to adjust the charts.
> Add resource requests/limits for the admission-controller
> ---------------------------------------------------------
>
> Key: YUNIKORN-536
> URL: https://issues.apache.org/jira/browse/YUNIKORN-536
> Project: Apache YuniKorn
> Issue Type: Task
> Components: shim - kubernetes
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.10
>
>
> We need to specify resource requests/limits for the admission-controller.
> Start the pod as a best-effort QoS class could possibly cause issues when the
> node is under heavy load. That can slow down the admission-controller and
> subsequentially slows down the api-server.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
