You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Jordan Zimmerman (Jira)" <ji...@apache.org> on 2025/06/11 08:41:00 UTC

[jira] [Created] (YUNIKORN-3088) admissionController.filtering.processNamespaces doesn't appear to work correctly

Jordan Zimmerman created YUNIKORN-3088:
------------------------------------------

             Summary: admissionController.filtering.processNamespaces doesn't appear to work correctly
                 Key: YUNIKORN-3088
                 URL: https://issues.apache.org/jira/browse/YUNIKORN-3088
             Project: Apache YuniKorn
          Issue Type: Bug
            Reporter: Jordan Zimmerman
             Fix For: 1.6.3


We want YuniKorn to operate on only 1 namespace so we are setting {{admissionController.filtering.processNamespaces}} in {{yunikorn-configs}} to that namespace. However I see in the YuniKorn logs {{Adding occupied resources to node}} for pods in other namespaces. Why is this? Is this expected? Are we doing something wrong? (note: we have the Admission controller disabled via Helm chart value).

E.g. the following pods/namespace should not be managed


{code}
2025-06-11T08:05:22.304Z	INFO	shim.cache.external	external/scheduler_cache.go:311	Adding occupied resources to node	{"nodeID": "k3d-test-agent-0", "namespace": "starburst-spark", "podName": "h-history-m-796bdc4d7c-zdpmb", "occupied": "resources:{key:\"memory\"  value:{value:524288000}}  resources:{key:\"pods\"  value:{value:1}}  resources:{key:\"vcore\"  value:{value:500}}"}
2025-06-11T08:05:22.304Z	INFO	shim.cache.external	external/scheduler_cache.go:311	Adding occupied resources to node	{"nodeID": "k3d-test-agent-0", "namespace": "starburst-spark", "podName": "prometheus-kube-prometheus-stack-prometheus-0", "occupied": "resources:{key:\"pods\"  value:{value:1}}"}
2025-06-11T08:05:22.304Z	INFO	shim.cache.external	external/scheduler_cache.go:311	Adding occupied resources to node	{"nodeID": "k3d-test-agent-0", "namespace": "starburst-sep", "podName": "coordinator-7fc569ddbf-dn7f8", "occupied": "resources:{key:\"memory\"  value:{value:3221225472}}  resources:{key:\"pods\"  value:{value:1}}  resources:{key:\"vcore\"  value:{value:500}}"}
2025-06-11T08:05:22.304Z	INFO	shim.cache.external	external/scheduler_cache.go:311	Adding occupied resources to node	{"nodeID": "k3d-test-server-0", "namespace": "starburst-spark", "podName": "starburst-spark-job-manager-7b8fb4bd65-jgjzs", "occupied": "resources:{key:\"pods\"  value:{value:1}}"}
{code}




--
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