[
https://issues.apache.org/jira/browse/YUNIKORN-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg updated YUNIKORN-28:
------------------------------------------
Fix Version/s: (was: 0..8)
0.8
> Support validating yunikorn-configs before admitting it
> -------------------------------------------------------
>
> Key: YUNIKORN-28
> URL: https://issues.apache.org/jira/browse/YUNIKORN-28
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Tao Yang
> Assignee: Tao Yang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Currently queues configuration are managed as ConfigMap, it can be easily
> updated via kubectl commands but won't be validated for now, thus this
> configmap may be inconsistent after been updated with invalid content, in
> this state, configmap is updated successfully while the scheduler is still
> using the previous configs, and the client doesn't know whether or not this
> update is succeed. This may leads to many unexpected results, for example,
> scheduler may not be successfully launched after restart.
> To improve the management for configs, we can add validations for yunikorn
> configs via admission-controller mechanism in K8S which is already used for
> mutations on pod's spec/metadata in yunikorn-k8shim.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
