v1beta2 wishlist

[alculquicondor]

What would you like to be cleaned:

In a v1beta2 API, we would like to make the following breaking changes:

• Workload
  • Report resource usage by pod, instead of the entire podset, in the admission struct.
  • Remove 'kueue.x-k8s.io/original-node-selectors' annotation
• LocalQueue
  • Rename status.flavorUsage to status.flavorsUsage.

Why is this needed:

As we add more features, some field didn't age well.

[tenzen-y]

Remove 'kueue.x-k8s.io/original-node-selectors' annotation from workload

ref: #771

[lowang-bh]

Has been removed in #834

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[tenzen-y]

/remove-lifecycle stale

[PBundyra]

Remove .spec.AdmissionChecks field in ClusterQueue and convert its content to .spec.AdmissionCheckStrategy
KEP: #1935
Issue: #1432

[IrvingMg]

Change .spec.flavorFungibility, .spec.preemption, .spec.preemption.borrowWithinCohort type from pointer to value for ClusterQueueSpec.
Discussion: #1972 (comment)

[mimowo]

Maybe we can consider to move the workload's spec.active to status.
Currently, the workload_controller needs write access to spec, which isn't recommended (see API conventions). Also, it makes tricky to set the reason for workload's deactivation reliably, see thread.

[alculquicondor]

I'm not too sure about that one. active expresses a desired state, as such, it should be in the spec. It can come from the user or it can come from the system.

[tenzen-y]

I'm not too sure about that one. active expresses a desired state, as such, it should be in the spec. It can come from the user or it can come from the system.

That is a good point.
In my point, I'm wondering if we should define the dedicated API for the kueue-controller-manager to deactivate the Workload in the status field.