Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
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.
