|
| 1 | +## v0.12.3 |
| 2 | + |
| 3 | +Changes since `v0.12.2`: |
| 4 | + |
| 5 | +## Urgent Upgrade Notes |
| 6 | + |
| 7 | +### (No, really, you MUST read this before you upgrade) |
| 8 | + |
| 9 | +- Helm: |
| 10 | + |
| 11 | + - Fixed KueueViz installation when enableKueueViz=true is used with default values for the image specifying parameters. |
| 12 | + - Split the image specifying parameters into separate repository and tag, both for KueueViz backend and frontend. |
| 13 | + |
| 14 | + If you are using Helm charts and installing KueueViz using custom images, |
| 15 | + then you need to specify them by kueueViz.backend.image.repository, kueueViz.backend.image.tag, |
| 16 | + kueueViz.fontend.image.repository and kueueViz.frontend.image.tag parameters. (#5514, @mbobrovskyi) |
| 17 | + |
| 18 | +## Changes by Kind |
| 19 | + |
| 20 | +### Feature |
| 21 | + |
| 22 | +- Allow setting the controller-manager's Pod `PriorityClassName` from the Helm chart (#5649, @kaisoz) |
| 23 | + |
| 24 | +### Bug or Regression |
| 25 | + |
| 26 | +- Add Cohort Go client library (#5603, @tenzen-y) |
| 27 | +- Fix the bug that Job deleted on the manager cluster didn't trigger deletion of pods on the worker cluster. (#5607, @ichekrygin) |
| 28 | +- Fix the bug that Kueue, upon startup, would incorrectly admit and then immediately deactivate |
| 29 | + already deactivated Workloads. |
| 30 | + |
| 31 | + This bug also prevented the ObjectRetentionPolicies feature from deleting Workloads |
| 32 | + that were deactivated by Kueue before the feature was enabled. (#5629, @mbobrovskyi) |
| 33 | +- Fix the bug that the webhook certificate setting under `controllerManager.webhook.certDir` was ignored by the internal cert manager, effectively always defaulting to /tmp/k8s-webhook-server/serving-certs. (#5491, @ichekrygin) |
| 34 | +- Fixed bug that doesn't allow Kueue to admit Workload after queue-name label set. (#5714, @mbobrovskyi) |
| 35 | +- MultiKueue: Fix a bug that batch/v1 Job final state is not synced from Workload cluster to Management cluster when disabling the `MultiKueueBatchJobWithManagedBy` feature gate. (#5706, @ichekrygin) |
| 36 | +- TAS: fix the bug which would trigger unnecessary second pass scheduling for nodeToReplace |
| 37 | + in the following scenarios: |
| 38 | + 1. Finished workload |
| 39 | + 2. Evicted workload |
| 40 | + 3. node to replace is not present in the workload's TopologyAssignment domains (#5591, @mimowo) |
| 41 | +- TAS: fix the scenario when deleted workload still lives in the cache. (#5605, @mimowo) |
| 42 | +- Use simulation of preemption for more accurate flavor assignment. |
| 43 | + In particular, in certain scenarios when preemption while borrowing is enabled, |
| 44 | + the previous heuristic would wrongly state that preemption was possible. (#5700, @gabesaba) |
| 45 | +- Use simulation of preemption for more accurate flavor assignment. |
| 46 | + In particular, the previous heuristic would wrongly state that preemption |
| 47 | + in a flavor was possible even if no preemption candidates could be found. |
| 48 | + |
| 49 | + Additionally, in scenarios when preemption while borrowing is enabled, |
| 50 | + the flavor in which reclaim is possible is preferred over flavor where |
| 51 | + priority-based preemption is required. This is consistent with prioritizing |
| 52 | + flavors when preemption without borrowing is used. (#5740, @gabesaba) |
| 53 | + |
1 | 54 | ## v0.12.2 |
2 | 55 |
|
3 | 56 | Changes since `v0.12.1`: |
|
0 commit comments