Michał Woźniak

Ok, but still I think Kueue, when running, could validate the integrations list exactly, based on the registered ones, as suggested in https://github.com/kubernetes-sigs/kueue/issues/4659#issuecomment-2732301613. Now, when it comes to the external...

This looks very similar to what we do in [Topology Aware Scheduling](https://github.com/kubernetes-sigs/kueue/issues/2724). IIUC this could be a special case for a topology with a single level corresponding to an individual...

I see, so the new proposed AdmissionCheck is somewhere between TAS and check-capacity in CA: differences with TAS: - simpler (faster) scheduling than TAS - compatible with other features (but...

@hy00nc thank you for being one of the early testers or TAS. I think what is want is already achievable if you use the 'preferred' annotation on your PodSet. Then...

"preferred" still means you need to have enough capacity, it just means that multiple nodes can be used (but their number will remain optimized). TAS operates on pod counts more...

Cool, this -3 is obviously a bug. I will try to repro and fix for 0.9.1, but in the meanwhile any additional repro steps will be very helpful for us....

+1 for opening an issue I understand the full yamls might be confidential, but you could probably share some of the most important bits of information for repro: - size...

Thank you for the summary. I totally understand the production reality where you need to support users on 1.29 whilst it is not yet supported by CA check-capacity. In principle...

Just a little bit of motivation, this will allow us: - reduce the amount of logging for not installed CRDs - shorten the time for the API to be ready...

/remove-lifecycle stale