Michał Woźniak
Michał Woźniak
> 1. `kubectl describe` can't access information from cache or even trigger an on-the-fly computation, unless it's all client-side. Unless I misunderstood the suggestion. I was hoping to be able...
> @mimowo Which cache are you referring to? The Kueue's server side cache. There is server-side printing: https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/#additional-printer-columns, but apparently it only allows to use `jsonPath` syntax to compute the...
I’m going to propose a design doc in a PR. Still, I would like to first ask some questions and discuss the overall approach I'm thinking about. First, I would...
> You also need to think about how to communicate the information to kueue internals. The Workload controller shouldn't know about Job. So maybe kueue's job controller can add a...
Please review the design doc: https://github.com/kubernetes-sigs/kueue/pull/433 @alculquicondor @kerthcet @ahg-g
> > nothing left on the functionality front, right? > > timeouts :) That is correct, we also planned to timeout workloads taking long to start (reaching the PodsReady=true state)....
> This is not functional, but maybe we want to update the documentation. I'm going to work on that. The place you pointed out might be good to show an...
> At least one integration test is flaky #488 A PR to fix the tests is opened https://github.com/kubernetes-sigs/kueue/pull/491, please review. Changes to the code don't seem necessary.
The PR to enforce PodsReady timeout (https://github.com/kubernetes-sigs/kueue/pull/498) is merged and the PR with docs is on the way: https://github.com/kubernetes-sigs/kueue/pull/515. Testing and feedback on the feature would be great! As discussed...