[YUNIKORN-941] split scheduler and admission controller deployment

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.12.2
• Component/s: shim - kubernetes
• Labels: pull-request-available
• Target Version: 0.12.2
• Assignee: Craig Condit
• Reporter: Kinga Marton
• Created: 15/Nov/21 13:02
• Updated: 03/Feb/22 22:52
• Resolved: 11/Jan/22 17:14

Description

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. 

Issue Links

• contains: YUNIKORN-995 Use v1 for ClusterRoleBinding rbac.authorization.k8s.io instead of v1beta1
• fixes: YUNIKORN-938 Admission controller: remove v1beta1 usage
• fixes: YUNIKORN-947 Add missing fields to the admission wehooks
• supercedes: YUNIKORN-625 Use v1 for CertificateSigningRequest instead of v1beta1
• supercedes: YUNIKORN-726 Quick start results in admission controller crashloop back off.
• links to: GitHub Pull Request #60
• links to: GitHub Pull Request #331
• links to: GitHub Pull Request #346