[
https://issues.apache.org/jira/browse/YUNIKORN-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071713#comment-17071713
]
Adam Antal commented on YUNIKORN-42:
------------------------------------
I have reviewed the code, let me paste my opinion here as well.
bq. I read the discussion in the jira. Though I agree with @wilfred-s regarding
the event publishing, I think for existing K8s users the `kubectl describe` is
a must - this is the most handful tool a kubernetes admin to look at. IMO we
should seek a way to only emit K8s relevant scheduling events and if the user
wants some more granular scheduler diagnostics, should try to look for the
YuniKorn UI or REST API.
> Better to support POD events for YuniKorn to troubleshoot allocation failures
> -----------------------------------------------------------------------------
>
> Key: YUNIKORN-42
> URL: https://issues.apache.org/jira/browse/YUNIKORN-42
> Project: Apache YuniKorn
> Issue Type: Task
> Reporter: Wangda Tan
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Now it is tricky to do troubleshoot for pod allocation, we need better expose
> this information to POD description.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
