[
https://issues.apache.org/jira/browse/YUNIKORN-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-706.
--------------------------------------------
Target Version: 1.0.0
Resolution: Fixed
thank you for your contribution changes are merged.
> Fix the resource calculation when the pod has init-containers
> -------------------------------------------------------------
>
> Key: YUNIKORN-706
> URL: https://issues.apache.org/jira/browse/YUNIKORN-706
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Weiwei Yang
> Assignee: Chen Yu Teng
> Priority: Critical
> Labels: newbie
> Fix For: 1.0.0
>
> Attachments: default_scheduler.png,
> image-2021-07-21-12-01-36-593.png, resource_usage _with_initcontainer.txt,
> web_app.png, web_node.png, yunikorn_scheduler.png
>
>
> Init-container resources currently got skipped:
> Steps to reproduce:
> # Submit pod with init containers.
> # Check UI for app allocations. It only displays the container request of
> 50m/50M, and not the initContainer request of 100m/100M.
> {code:java}
> 9650-mbp15-rozhang:~ rozhang$ kubectl get pods -n dev
> NAME READY STATUS RESTARTS AGE
> app-4 0/1 Init:0/1 0 5s
> {code}
> From describe node, we see requests of 100m/100M, which is not the same as
> Yunikorn.
> Related doc:
> https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#resources.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
