Decide if we release kjobctl as part of Kueue

kubernetes-sigs / kueue

Kubernetes-native Job Queueing

https://kueue.sigs.k8s.io

Apache License 2.0

1.38k stars 251 forks source link

Decide if we release kjobctl as part of Kueue #2778

Open mimowo opened 2 months ago

mimowo commented 2 months ago

We started to develop kjobctl inside Kueue (cmd/experimental/kjobctl) to get quickly off the ground.

This lets us develop quickly, and may be handy for a while yet.

However, in the long run we discussed that the plan is to move it at some point to a dedicated kubernetes-sigs subproject.

Until that happens - should we release it as part of Kueue release process (exposing the artifacts)?

mimowo commented 2 months ago

/cc @alculquicondor @mwielgus @tenzen-y I open this as a follow up to https://github.com/kubernetes-sigs/kueue/pull/2642.

tenzen-y commented 2 months ago

TBH, I'm ok with either approach. But, I'm wondering if we can create separate repository since I'm not familiar with criterion for new repositories in the k-sigs org.

I just want to say that we should commonize all duplicated scripts as root scripts when we decide to we manage kjobctl in this repository.

mbobrovskyi commented 1 month ago

@alculquicondor WDYT?

alculquicondor commented 1 month ago

We can split after we have the MVP, to avoid disrupting the developer flow.