[
https://issues.apache.org/jira/browse/YUNIKORN-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit resolved YUNIKORN-1113.
------------------------------------
Fix Version/s: 1.0.0
Resolution: Fixed
Merged to master. Thanks [~sunilg] for the review.
> 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
> Labels: pull-request-available
> Fix For: 1.0.0
>
>
> 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 fix connectivity issues between
> scheduler and admission controller when running in host mode.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
