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-1112) Use Kubernetes ENV vars for locating yunikorn service from admission controller
[ https://issues.apache.org/jira/browse/YUNIKORN-1112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Craig Condit updated YUNIKORN-1112:
-----------------------------------
Description:
Currently, we call out to the yunikorn service from within the admission controller to do config validations. This requires that yunikorn be reachable by the admission controller for validation succeed. When running under environments such as EKS with Calico, the services are not able to see one another when connecting to the yunikorn service address. However, Kubernetes provides several environment variables which can be used for this purpose:
YUNIKORN_SERVICE_SERVICE_HOST=\{snip}
YUNIKORN_SERVICE_SERVICE_PORT=9080
These are visible and reachable from within the admission controller container, even though yunikorn-service is unresolvable.
was:Currently, we call out to the yunikorn service from within the admission controller to do config validations. This requires that yunikorn be up, healthy, and reachable by the admission controller for validation succeed. We should embed the validation logic in the admission controller itself to decouple the two components.
Issue Type: Bug (was: Improvement)
Summary: Use Kubernetes ENV vars for locating yunikorn service from admission controller (was: Embed config validation logic into admission controller)
> Use Kubernetes ENV vars for locating yunikorn service from admission controller
> -------------------------------------------------------------------------------
>
> Key: YUNIKORN-1112
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1112
> Project: Apache YuniKorn
> Issue Type: Bug
> Components: shim - kubernetes
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
> Fix For: 1.0.0
>
>
> Currently, we call out to the yunikorn service from within the admission controller to do config validations. This requires that yunikorn be reachable by the admission controller for validation succeed. When running under environments such as EKS with Calico, the services are not able to see one another when connecting to the yunikorn service address. However, Kubernetes provides several environment variables which can be used for this purpose:
>
> YUNIKORN_SERVICE_SERVICE_HOST=\{snip}
> YUNIKORN_SERVICE_SERVICE_PORT=9080
>
> These are visible and reachable from within the admission controller container, even though yunikorn-service is unresolvable.
>
>
--
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