You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2022/03/11 17:26:00 UTC

[jira] [Updated] (YUNIKORN-1113) Allow admission controller / scheduler to run in host network

     [ https://issues.apache.org/jira/browse/YUNIKORN-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Condit updated YUNIKORN-1113:
-----------------------------------
    Issue Type: Bug  (was: Improvement)

> Allow admission controller / scheduler to run in host network
> -------------------------------------------------------------
>
>                 Key: YUNIKORN-1113
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1113
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: shim - kubernetes
>            Reporter: Craig Condit
>            Assignee: Craig Condit
>            Priority: Major
>
> In certain environments (such as EKS with Calico) it is necessary to run the admission controller in the host network to allow the control plane to reach it. We should provide helm  variables to change the default for each.
> I think we should default the admission controller to hostNetwork: true as this will provide the broadest compatibility with the widest network configurations.
> Additionally, the yunikorn service should default to hostNetwork: false to allow for better isolation. 
>  
> I have opened YUNIKORN-1112 as well to cover refactoring the configmap validation logic to keep the admission controller independent of the scheduler.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org