build(deps): bump sigs.k8s.io/kueue from 0.19.2 to 0.19.3

[dependabot]

Bumps sigs.k8s.io/kueue from 0.19.2 to 0.19.3.

Release notes

Sourced from sigs.k8s.io/kueue's releases.

v0.19.3

Changes since v0.19.2:

Actions Required Before Upgrading

(No, really, you MUST read this before you upgrade)

• Minor releases: Review the .0 release notes for each new minor version you cross; see: v0.18.0, v0.19.0.

• Patch releases: Review the patch release notes leading up to this version, but only within this minor release line; see: v0.19.1, v0.19.2.

• DRA & ResourceTransformation: Fixed a bug where DRA device-class mapping or a resource transformation under the reserved resource name pods was silently discarded or left the Workload permanently pending.

  Remove or rename those entries before upgrading, or the kueue-controller-manager will fail to start. Renaming a mapping name or an outputs key also requires updating the matching ClusterQueue nominalQuota entries in the same change. (#14756, @​thc1006)

Changes by Kind

Feature

• WorkloadAwareScheduler: Added the kueue.x-k8s.io/workload annotation to Pods created by Kueue-managed jobs when the SchedulerLibraryIntegration feature gate is enabled; previously only TopologyAwareScheduling added it. (#14796, @​Singularity23x0)

Bug or Regression

• AdmissionChecks: Fix a bug where the Workload has an Admitted=True condition regardless of AdmissionCheck Rejection state. (#14871, @​TapanManu)
• AdmissionFairSharing: Fixed preemption ordering for Workloads from same-named LocalQueues in different namespaces so that LocalQueue usage is considered. (#14876, @​tomsen02)
• DRA: Fixed config validation silently accepting capacity names with more than one slash, which produced a mapping that never matched any device. (#14953, @​NasitSony)
• FairSharing: Fix a bug where Kueue could miss valid preemption targets after selecting workloads from the preemptor's own ClusterQueue and lowering its DRS. The fix is guarded by the Alpha FairSharingReevaluatePreemptionCandidates feature gate, which is disabled by default. Enabling the gate may increase exposure to the known fair-sharing preemption-loop issue tracked in #14543. (#14767, @​lightZebra)
• Fixed a bug where a prebuilt or externally created Workload could be treated as equivalent to its Job even when the Job's pod template declared pod-level resources or resourceClaims that the Workload's PodSet omitted, letting the Workload reserve less quota than its Pods actually request. (#15016, @​pujitha24)
• Fixed a controller panic triggered by Namespace updates after a ClusterQueue failed to initialize because its Cohort had a cycle. (#14983, @​YQ-Wang)
• Helm: Fix a bug where user-defined metricsService labels are not propagated to the rendered manifests. (#15005, @​HsiuChuanHsu)
• KueueCtl: Fixed a bug where kueuectl delete workload deleted a recreated owner with a different UID. (#14882, @​DevaanshPathak)
• KueueCtl: Fixed the kueuectl list clusterqueue comand to respect KUEUECTL_LIST_REQUEST_LIMIT and paginate API requests instead of issuing an unbounded LIST request. (#14880, @​ErikJiang)
• Kueueviz: Fixed the bug the WebSocket 1005 error would be shown on the dashboard after selecting a namespace. (#14789, @​mykysha)
• MultiKueue: Fixed a bug where a Job is dispatched again due to propagated spec.ttlSecondsAfterFinished even after Job completion. Enable the Alpha MultiKueueBatchJobClearingTTLSecondsAfterFinishedOnWorkerCluster feature gate to enable fixing. (#14828, @​kevin85421)
• MultiKueue: Fixed a bug where a remote workload finishing with reason OwnerNotFound was mirrored back verbatim, permanently finishing the manager Workload and leaving the manager Pod's scheduling gates stuck. Such finishes are now treated as a sync failure and reset for re-dispatch, matching existing OutOfSync handling. (#15082, @​NasitSony)
• MultiKueue: Fixed a bug where the WorkloadPriorityClass controller incorrectly updated the priority of MultiKueue remote workloads when a WorkloadPriorityClass value changed. Remote workloads are now skipped during priority synchronization. (#14995, @​weizhoublue)
• MultiKueue: Fixed stale observedGeneration on the AdmissionCheckActive condition after updating to a MultiKueueConfig that preserves the cluster health result. (#14915, @​cryo-zd)
• MultiKueue: Truncate quota automation condition messages so unsupported manager/worker resource configurations can be reported successfully. (#14989, @​cryo-zd)
• Observability: Fixed kueue_pod_scheduling_gate_removal_seconds observing negative durations when the controller clock trails the apiserver clock. The negative observations made the histogram's _sum decrease, which broke rate() over that series. (#14731, @​Antrikshgwal)
• Observability: Scheduling hash re-computations are now logged at V5 via the contextual logger. (#15060, @​apullo777)
• Pending Workloads rejected by a LimitRange are requeued when the LimitRange's max, min, or maxLimitRequestRatio change, or the LimitRange is deleted. (#15029, @​tomsen02)
• Pod: Fixed a bug where a serving pod group's evicted pod could be left stuck in Terminating forever, since its kueue.x-k8s.io/managed finalizer was only removed for a Workload deletion, not for other evictions (e.g. a recoveryTimeout eviction). This could cause a legitimate replacement pod to be deleted as excess instead, or permanently block a same-name (StatefulSet-owned) replacement from ever being created. Kueue now removes the finalizer as soon as an evicted pod has actually terminated. (#14793, @​mszadkow)
• ProvisioningRequest: Fixed a bug where the Active condition's observedGeneration on a ProvisioningRequest AdmissionCheck was not updated when a configuration change kept the check healthy, leaving observedGeneration permanently behind metadata.generation. (#14934, @​weizhoublue)
• RayService: Fixed a bug where elastic (autoscaling) RayService pods could stay stuck in SchedulingGated on kueue.x-k8s.io/elastic-job after the origin workload slice was deleted, leaving the RayCluster below its desired replica count. (#15103, @​kevin85421)
• Scheduling: Fix a bug in BestEffortFIFO where a workload with failed preemption could remain sticky at the queue head. (#15089, @​tenzen-y)
• Scheduling: Fix workloads becoming stranded after scheduling snapshot failures, and stale pending accounting when a LocalQueue moves to another ClusterQueue. (#13885, @​apullo777)

... (truncated)

Commits

• 2ade477 Prepare release v0.19.3 (#15108)
• 25068ce [release-0.19] Fix elastic ungating when pods and the Workload have different...
• 5087941 Add a restart regression spec for effective-resource accounting (#15037) (#15...
• 16af54c fix: clear sticky preemptorWorkload when preemption fails (#15089)
• 8005578 Remove unnecessary ctx in UpdateClusterQueue (#15086)
• bb239b5 multikueue: reset admission check for remote OwnerNotFound finish instead of ...
• 2ef80a1 rename var and cleanup (#15077)
• fb588d1 Lower the reserved-workload priority-transition skip log to V(4) (#15068)
• be7a582 Use NewInfoWithLogger for the remaining production Info construction (#15060)
• 57249aa Reuse the scheduling equivalence hash when a requeued workload is unchanged (...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)