You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2021/11/03 03:06:00 UTC
[jira] [Resolved] (YUNIKORN-927) Improve logging in the yunikorn
admission controller
[ https://issues.apache.org/jira/browse/YUNIKORN-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wilfred Spiegelenburg resolved YUNIKORN-927.
--------------------------------------------
Fix Version/s: 1.0.0
Resolution: Fixed
changes committed, logging should be clearer now
[~pbacsko] thank you
> Improve logging in the yunikorn admission controller
> ----------------------------------------------------
>
> Key: YUNIKORN-927
> URL: https://issues.apache.org/jira/browse/YUNIKORN-927
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> The logging in the admission controller is not providing the correct set of data.
> One case that jumps out is the label manipulation. The original set of labels is logged at an INFO level the modifications are not logged unless running at a DEBUG level. That makes the INFO level log of almost no use.
> We need to do a full review of the admission controller logging and make sure we can use it to troubleshoot.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org