kueue
kueue copied to clipboard
Deprecate the `QueueVisibility` feature gate and corresponding API
What would you like to be cleaned:
I suggest coming with a plan to deprecate the QueueVisibility
API. I would start with deprecating the QueueVisiblity
feature gate and deleting logic behind it, and then remove the visibility field from ClusterQueue's Status when migrating to a next beta version of Kueue API.
Why is this needed:
There was the visibility API introduced that covers all business needs that were cover by the QueueVisibility
API and more. The visibility API resolves all drawback related to the QueueVisibility
API and addresses its limitations. For now I don't see a rationale for maintaining the QueueVisiblity
API. Additionally I believe having two different ways (and two feature gates) to monitor pending workloads may lead to a little confusion regarding their pros and cons.