You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2024/05/13 10:13:00 UTC
[jira] [Assigned] (YUNIKORN-2621) CSINode informer is not started
[ https://issues.apache.org/jira/browse/YUNIKORN-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko reassigned YUNIKORN-2621:
--------------------------------------
Assignee: Jacob Salway
> CSINode informer is not started
> -------------------------------
>
> Key: YUNIKORN-2621
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2621
> Project: Apache YuniKorn
> Issue Type: Bug
> Reporter: Jacob Salway
> Assignee: Jacob Salway
> Priority: Minor
> Labels: pull-request-available
>
> The shared CSINode informer created in the shim is not started, meaning anything that uses CSINodes from the shared informer factory, such as any scheduler plugins like nodevolumelimits or the volume binder in Yunikorn itself.
> Two symptoms of this that we observed at Rokt was Yunikorn not respecting the allocatable field on CSINode objects and error logs from the volume binder about not being able to find CSINode objects.
> [https://github.com/apache/yunikorn-k8shim/blob/master/pkg/client/apifactory.go#L91]
> [https://github.com/apache/yunikorn-k8shim/blob/master/pkg/client/clients.go#L92-L101]
> [https://github.com/kubernetes/kubernetes/blob/v1.30.0/pkg/scheduler/framework/plugins/nodevolumelimits/csi.go#L120]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org