Michał Woźniak

cc @PBundyra ptal

> What's the context for this change @mbobrovskyi? I would add to the context that this is a "best effort" feature as we don't yet have users asking for this....

This feature is low priority for 0.12 (no users requesting) for the moment - yet it is tricky, so I will review it only "best effort", once the comments are...

This needs more adjustments to take into account the presence of the LQ "default", see https://github.com/kubernetes-sigs/kueue/pull/5451

We have the release candidate: https://github.com/kubernetes-sigs/kueue/releases/tag/v0.9.0-rc.1 Please test, report issues and propose fixes :) we are aiming for the full release 4th Nov.

I've updated the release notes, compared to v0.9.0-rc.1 the new entries are: - ProvisioningRequestConfig API has now `RetryStrategy` field that allows users to configure retries per ProvisioningRequest class. By default...

/kind flake /cc @trasc @mbobrovskyi @alculquicondor I know this is not in test code but it looks like infra, still opened the issue as it seemingly only happens for e2e...

Actually, I spotted the similar failure today for unit tests: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_kueue/3292/pull-kueue-test-unit-main/1849084700195295232 ``` go: downloading gotest.tools/gotestsum v1.12.0 go: gotest.tools/[email protected][2](https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_kueue/3292/pull-kueue-test-unit-main/1849084700195295232#1:build-log.txt%3A2).0: gotest.tools/[email protected]: verifying module: gotest.tools/[email protected]: Get "https://sum.golang.org/lookup/gotest.tools/[email protected]": dial tcp 142.250.190.49:44[3](https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_kueue/3292/pull-kueue-test-unit-main/1849084700195295232#1:build-log.txt%3A3): i/o timeout make:...

I've updated the title to reflect this is not just multikueue, even though it seems the most common there. EDIT: also started a thread on k8s-infra: https://kubernetes.slack.com/archives/CCK68P2Q2/p1729753129367449

> doc open? i assume "issue" open, I don't think there is, closing /close