Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
kueue-v0.13.1.spdx.json | 2025-08-01 | 12.3 MB | |
kueue.vex.json | 2025-08-01 | 251 Bytes | |
manifests.yaml | 2025-08-01 | 827.5 kB | |
prometheus.yaml | 2025-08-01 | 1.6 kB | |
visibility-apf.yaml | 2025-08-01 | 1.2 kB | |
manifests-alpha-enabled.yaml | 2025-08-01 | 827.5 kB | |
manifests-dev.yaml | 2025-08-01 | 827.5 kB | |
kueue-0.13.1.tgz | 2025-08-01 | 104.3 kB | |
kueueviz.yaml | 2025-08-01 | 4.4 kB | |
kubectl-kueue-linux-arm64.tar.gz | 2025-08-01 | 33.0 MB | |
kubectl-kueue-linux-arm64 | 2025-08-01 | 83.3 MB | |
kubectl-kueue-linux-amd64.tar.gz | 2025-08-01 | 35.2 MB | |
kubectl-kueue-darwin-amd64 | 2025-08-01 | 86.8 MB | |
kubectl-kueue-darwin-amd64.tar.gz | 2025-08-01 | 35.3 MB | |
kubectl-kueue-darwin-arm64 | 2025-08-01 | 84.6 MB | |
kubectl-kueue-darwin-arm64.tar.gz | 2025-08-01 | 33.9 MB | |
kubectl-kueue-linux-amd64 | 2025-08-01 | 86.2 MB | |
README.md | 2025-08-01 | 2.9 kB | |
v0.13.1 source code.tar.gz | 2025-08-01 | 17.8 MB | |
v0.13.1 source code.zip | 2025-08-01 | 25.9 MB | |
Totals: 20 Items | 537.0 MB | 0 |
Changes since v0.13.0
:
Urgent Upgrade Notes
(No, really, you MUST read this before you upgrade)
- Rename kueue-metrics-certs to kueue-metrics-cert cert-manager.io/v1 Certificate name in cert-manager manifests when installing Kueue using the Kustomize configuration.
If you're using cert-manager and have deployed Kueue using the Kustomize configuration, you must delete the existing kueue-metrics-certs cert-manager.io/v1 Certificate before applying the new changes to avoid conflicts. (#6362, @mbobrovskyi)
Changes by Kind
Bug or Regression
- Fix accounting for the
evicted_workloads_once_total
metric: - the metric wasn't incremented for workloads evicted due to stopped LocalQueue (LocalQueueStopped reason)
- the reason used for the metric was "Deactivated" for workloads deactivated by users and Kueue, now the reason label can have the following values: Deactivated, DeactivatedDueToAdmissionCheck, DeactivatedDueToMaximumExecutionTimeExceeded, DeactivatedDueToRequeuingLimitExceeded. This approach aligns the metric with
evicted_workloads_total
. - the metric was incremented during preemption before the preemption request was issued. Thus, it could be incorrectly over-counted in case of the preemption request failure.
- the metric was not incremented for workload evicted due to NodeFailures (TAS)
The existing and introduced DeactivatedDueToXYZ reason label values will be replaced by the single "Deactivated" reason label value and underlying_cause in the future release. (#6360, @mimowo) - Fix the bug for the ElasticJobsViaWorkloadSlices feature where in case of Job resize followed by eviction of the "old" workload, the newly created workload could get admitted along with the "old" workload. The two workloads would overcommit the quota. (#6257, @ichekrygin) - Fix the bug which could occasionally cause workloads evicted by the built-in AdmissionChecks (ProvisioningRequest and MultiKueue) to get stuck in the evicted state which didn't allow re-scheduling. This could happen when the AdmissionCheck controller would trigger eviction by setting the Admission check state to "Retry". (#6299, @mimowo) - Fixed a bug that prevented adding the kueue- prefix to the secretName field in cert-manager manifests when installing Kueue using the Kustomize configuration. (#6343, @mbobrovskyi) - ProvisioningRequest: Fix a bug that Kueue didn't recreate the next ProvisioningRequest instance after the second (and consecutive) failed attempt. (#6329, @PBundyra) - Support disabling client-side ratelimiting in Config API clientConnection.qps with a negative value (e.g., -1) (#6305, @tenzen-y) - TAS: Fix a bug that the node failure controller tries to re-schedule Pods on the failure node even after the Node is recovered and reappears (#6347, @pajakd)