You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2022/01/06 10:29:00 UTC

[jira] [Commented] (YUNIKORN-941) split scheduler and admission controller deployment

    [ https://issues.apache.org/jira/browse/YUNIKORN-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469824#comment-17469824 ] 

Wilfred Spiegelenburg commented on YUNIKORN-941:
------------------------------------------------

The admission controller code has been updated since the draft of this change went in. I think it is better to finish the change from v1beta1 to the v1 version via YUNIKORN-938. It can be handled separately and without making changes to the way we do the certs etc.

I have asked [~pbacsko] to look at that jira.

> split scheduler and admission controller deployment
> ---------------------------------------------------
>
>                 Key: YUNIKORN-941
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-941
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: shim - kubernetes
>            Reporter: Kinga Marton
>            Assignee: Craig Condit
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: logs_322.zip
>
>
> To support proper YuniKorn upgrades and restarts we should move the admission controller out of the scheduler deployment and make it a separate deployment.
> This could also allow the admission controller to be made high available and allow simpler no down time upgrades possible. 



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