Michał Woźniak

FYI I asked around and it seems if we want to move it to separate repo the next step would be to create an issue analogus to [this one for...

> Which SIGs sponsor kjobctl? I guess sig-apps? This seems the most natural fit. > I guess that we need to negotiate with the SIG lead in advance. I see,...

Or alternatively, do you think we could move the project under umbrella of being sponsored by wg-batch?

The next sig-apps meeting will probably be after KubeCon, so Nov 25, we can raise it then.

FYI we are already presenting the kjobctl as an idea at the [wg-batch meeting Jun 6th, 2024](https://docs.google.com/document/d/1XOeUN-K0aKmJJNq7H07r74n-mGgSFyiEDQ3ecwsGhec).

cc @soltysh as sig-apps lead to also align on the next steps here.

> Based on my understanding kjobctl is tightly coupled with kueue, and reading through comments that also holds on the code level. I think this is not correct, kjobctl is...

FYI: we have the new and shiny repo: https://github.com/kubernetes-sigs/kjob. The code is perfectly clean :)

So, there are two things at play here, IIUC: 1. why GKE does not provision successfully the ProvisioningRequest sometimes when using `queued-provisioning.gke.io` - I would leave this issue to the...

cc @PBundyra who also worked on AdmissionChecks at some point and may have some idea on why the workload wasn't retried by Kueue