[Umbrella] ☂️ Requirements for release 0.2.0

[ahg-g]

Issues that we need to complete to consider Kueue ready for the second release:

I suggest to focus only on issues related to Productionisation:

• Knobs to configure which jobs Kueue manages
• More detailed pending event
• Handle Pod overhead added during pod admission
• Add "Frozen" ClusterQueue state
• Rename image to registry.k8s.io/kueue/kueue
• Manage webhook cert internally
• Trigger the movement of workload in ClusterQueue by ns event
• Add webhook for APIs defaulting and validation
  • Validate resources that share the same flavors in a ClusterQueue #308
• Add ClusterQueue and Queue Metrics
  • Add label to pending_workloads metric to show the inadmissible workloads #324
• Using the same flavors in different resources might lead to unschedulable pods
• Avoid queueing workloads that don't match CQ namespaceSelector
• Should we use server-side apply for admission?
• Rename the namespaced resource "Queue"
• Update docs

Nice to have:

• Add real E2E test setup and first test
• Add scalability tests

[ahg-g]

Our backlog of features is listed below, but I think we shouldn't add any more features before closing our backlog of productionization/hardening related issues:

• Support Spark jobs specifically and dynamically sized jobs
• Support kubeflow's MPIJob
• Replace borrowing ceiling with weights
• Workload preemption
• Simple Framework to support different queuing policies
• Budgets
• Hierarchical ClusterQueues
• Include ClusterQueue depth in Workload status

@alculquicondor @denkensk @ArangoGutierrez @kerthcet what do you think?

[kerthcet]

Glad to see a backlog here, do we have a rough deadline?

[denkensk]

Our backlog of features is listed below, but I think we shouldn't add any more features before closing our backlog of productionization/hardening related issues.

sgtm.

[ArangoGutierrez]

lgtm

[alculquicondor]

+1

[alculquicondor]

#226 to be good k8s citizens :)

[alculquicondor]

#232 to simplify deployment of webhooks

[ahg-g]

Should we set a deadline as @kerthcet suggested? Perhaps after KubeCon?

[alculquicondor]

I think we still have a lot to solve, so I wouldn't bet on a release within a week of Kubecon. Maybe June 15th for the batch live panel? https://opensourcelive.withgoogle.com/learn-kubernetes

[ArangoGutierrez]

226 is closed now :)

[kerthcet]

Maybe we can release regularly to avoid similar discussion later. Features are always there.

[alculquicondor]

FYI
@ahg-g and I will be in kubecon next week (May 16th), so we might have limited time to approve PRs.
The week after, we are both out on vacation (May 23th).
I'll be back in May 30th.

[denkensk]

@ahg-g @alculquicondor Have a nice vacation!
I could probably spend more time fixing some urgent issues and reviewing code.

[kerthcet]

Have a wonderful speech 🚀, and I'll help on reviewing the same time.

[ahg-g]

consider adding #103 to this release as well

[kerthcet]

consider adding #103 to this release as well

I'm already in settling the deletion part of the work.

[kerthcet]

What is left for v0.2.0, it seems the necessary ones are all finished.

[alculquicondor]

#341, update API version to v1alpha2, and update documentation

[alculquicondor]

Started the release checklist in #352

[ahg-g]

/close

[k8s-ci-robot]

@ahg-g: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.