What would you like to be added:
I would like to re-implement the manageJobsWithoutQueueName as MAPs generator.
So, if cluster admins enable the feature, the kueue-controller-manager just creates the MAPs for enabled Jobs,
and then we will remove the current webhook mechanism.
Why is this needed:
The current manageJobsWithoutQueueName is implemented as a webhook, and the webhook will be called many times based on the Jobs creation. In the large cluster, the many webhook calls increase the kube-apiserver load, and it will make the cluster slow down.
So, I would recommend re-implement the mechanism as a MAP generator since the MAPs are evaluated within the kube-apiserver and will not all external webhook servers (kueue-controller-manager).
Completion requirements:
This enhancement requires the following artifacts:
[x] Design doc
[ ] API change
[ ] Docs update
The artifacts should be linked in subsequent comments.
What would you like to be added: I would like to re-implement the manageJobsWithoutQueueName as MAPs generator. So, if cluster admins enable the feature, the kueue-controller-manager just creates the MAPs for enabled Jobs, and then we will remove the current webhook mechanism.
Why is this needed: The current manageJobsWithoutQueueName is implemented as a webhook, and the webhook will be called many times based on the Jobs creation. In the large cluster, the many webhook calls increase the kube-apiserver load, and it will make the cluster slow down.
So, I would recommend re-implement the mechanism as a MAP generator since the MAPs are evaluated within the kube-apiserver and will not all external webhook servers (kueue-controller-manager).
Completion requirements:
This enhancement requires the following artifacts:
The artifacts should be linked in subsequent comments.
Note that MutatingAdmisionPolicy is still alpha in v1.32 (https://github.com/kubernetes/enhancements/issues/3962). So, we can consider this after the Beta graduation.