Prepare release v0.15.3

Author: gabesaba

CHANGELOG/CHANGELOG-0.15.md

@@ -1,3 +1,45 @@
+## v0.15.3
+
+Changes since `v0.15.2`:
+
+## Changes by Kind
+
+### Feature
+
+- CLI: Support "kwl" and "kueueworkload" as a shortname for Kueue Workloads. (#8469, @k8s-infra-cherrypick-robot)
+
+### Bug or Regression
+
+- Add lws editer and viewer roles to kustomize and helm (#8515, @k8s-infra-cherrypick-robot)
+- FailureRecovery: Fix Pod Termination Controller's MaxConcurrentReconciles (#8665, @k8s-infra-cherrypick-robot)
+- Fix ClusterQueue deletion getting stuck when pending workloads are deleted after being assumed by the scheduler. (#8548, @k8s-infra-cherrypick-robot)
+- Fix a bug that WorkloadPriorityClass value changes do not trigger Workload priority updates. (#8499, @ASverdlov)
+- HC: Avoid redundant requeuing of inadmissible workloads when multiple ClusterQueues in the same cohort hierarchy are processed. (#8510, @k8s-infra-cherrypick-robot)
+- Integrations based on Pods: skip using finalizers on the Pods created and managed by integrations. 
+  
+  In particular we skip setting finalizers for Pods managed by the built in Serving Workloads  Deployments,
+  StatefulSets, and LeaderWorkerSets.
+  
+  This improves performance of suspending the workloads, and fixes occasional race conditions when a StatefulSet
+  could get stuck when deactivating and re-activating in a short interval. (#8573, @mbobrovskyi)
+- JobFramework: Fixed a bug that allowed a deactivated workload to be activated. (#8438, @k8s-infra-cherrypick-robot)
+- LeaderWorkerSet: Fixed a bug that prevented deleting the workload when the LeaderWorkerSet was scaled down. (#8673, @mbobrovskyi)
+- MultiKueue now waits for WorkloadAdmitted (instead of QuotaReserved) before deleting workloads from non-selected worker clusters. To revert to the previous behavior, disable the `MultiKueueWaitForWorkloadAdmitted` feature gate. (#8600, @IrvingMg)
+- MultiKueue: Fix a bug that the priority change by mutating the `kueue.x-k8s.io/priority-class` label on the management cluster is not propagated to the worker clusters. (#8574, @mbobrovskyi)
+- MultiKueue: fix the eviction when initiated by the manager cluster (due to eg. Preemption or WairForPodsReady timeout). (#8402, @mbobrovskyi)
+- ProvisioningRequest: Fixed a bug that prevented events from being updated when the AdmissionCheck state changed. (#8404, @mbobrovskyi)
+- Revert the changes in PR https://github.com/kubernetes-sigs/kueue/pull/8599 for transitioning
+  the QuotaReserved, Admitted conditions to `False` for Finished workloads. This introduced a regression,
+  because users lost the useful information about the timestamp of the last transitioning of these
+  conditions to True, without an API replacement to serve the information. (#8612, @mbobrovskyi)
+- Scheduling: fix the bug that setting (none -> some) a workload priority class label (kueue.x-k8s.io/priority-class) was ignored. (#8584, @andrewseif)
+- TAS: Fix a bug that MPIJob with runLauncherAsWorker Pod indexes are not correctly evaluated during rank-based ordering assignments. (#8663, @tenzen-y)
+- TAS: Fixed an issue where workloads could remain in the second-pass scheduling queue (used for integration
+  or TAS with ProvisioningRequests, and for TAS Node Hot Swap) even if they no longer require to be in the queue. (#8431, @skools-here)
+- TAS: fix TAS resource flavor controller to extract only scheduling-relevant node updates to prevent unnecessary reconciliation. (#8453, @k8s-infra-cherrypick-robot)
+- TAS: significantly improves scheduling performance by replacing Pod listing with an event-driven
+  cache for non-TAS Pods, thereby avoiding expensive DeepCopy operations during each scheduling cycle. (#8484, @gabesaba)
+
 ## v0.15.2
 
 Changes since `v0.15.1`:

Makefile

@@ -91,7 +91,7 @@ LD_FLAGS += -X '$(version_pkg).BuildDate=$(shell date -u +%Y-%m-%dT%H:%M:%SZ)'
 
 # Update these variables when preparing a new release or a release branch.
 # Then run `make prepare-release-branch`
-RELEASE_VERSION=v0.15.2
+RELEASE_VERSION=v0.15.3
 RELEASE_BRANCH=release-0.15
 # Application version for Helm and npm (strips leading 'v' from RELEASE_VERSION)
 APP_VERSION := $(shell echo $(RELEASE_VERSION) | cut -c2-)

README.md

@@ -62,7 +62,7 @@ Read the [overview](https://kueue.sigs.k8s.io/docs/overview/) and watch the Kueu
 To install the latest release of Kueue in your cluster, run the following command:
 
 ```shell
-kubectl apply --server-side -f https://github.com/kubernetes-sigs/kueue/releases/download/v0.15.2/manifests.yaml
+kubectl apply --server-side -f https://github.com/kubernetes-sigs/kueue/releases/download/v0.15.3/manifests.yaml
 ```
 
 The controller runs in the `kueue-system` namespace.

charts/kueue/Chart.yaml

@@ -16,9 +16,9 @@ type: application
 # NOTE: Do not modify manually. In Kueue, the version and appVersion are
 # overridden to GIT_TAG when building the artifacts, including the helm charts,
 # via Makefile.
-version: 0.15.2
+version: 0.15.3
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to
 # follow Semantic Versioning. They should reflect the version the application is using.
 # It is recommended to use it with quotes.
-appVersion: "v0.15.2"
+appVersion: "v0.15.3"

charts/kueue/README.md

@@ -1,6 +1,6 @@
 # kueue
 
-![Version: 0.15.2](https://img.shields.io/badge/Version-0.15.2-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.15.2](https://img.shields.io/badge/AppVersion-v0.15.2-informational?style=flat-square)
+![Version: 0.15.3](https://img.shields.io/badge/Version-0.15.3-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v0.15.3](https://img.shields.io/badge/AppVersion-v0.15.3-informational?style=flat-square)
 
 Kueue is a set of APIs and controllers for job queueing. It is a job-level manager that decides when a job should be admitted to start (as in pods can be created) and when it should stop (as in active pods should be deleted).
 
@@ -28,7 +28,7 @@ $ helm install kueue kueue/ --create-namespace --namespace kueue-system
 Or use the charts pushed to `oci://registry.k8s.io/kueue/charts/kueue`:
 
 ```bash
-helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.2" --create-namespace --namespace=kueue-system
+helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.3" --create-namespace --namespace=kueue-system
 ```
 
 For more advanced parametrization of Kueue, we recommend using a local overrides file, passed via the `--values` flag. For example:
@@ -50,15 +50,15 @@ controllerManager:
 ```
 
 ```bash
-helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.2" \
+helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.3" \
   --create-namespace --namespace=kueue-system \
   --values overrides.yaml
 ```
 
 You can also use the `--set` flag. For example, to enable a feature gate (e.g., `TopologyAwareScheduling`):
 
 ```bash
-helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.2" \
+helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.3" \
   --create-namespace --namespace=kueue-system \
   --set "controllerManager.featureGates[0].name=TopologyAwareScheduling" \
   --set "controllerManager.featureGates[0].enabled=true"

charts/kueue/README.md.gotmpl

@@ -30,7 +30,7 @@ $ helm install kueue kueue/ --create-namespace --namespace kueue-system
 Or use the charts pushed to `oci://registry.k8s.io/kueue/charts/kueue`:
 
 ```bash
-helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.2" --create-namespace --namespace=kueue-system
+helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.3" --create-namespace --namespace=kueue-system
 ```
 
 For more advanced parametrization of Kueue, we recommend using a local overrides file, passed via the `--values` flag. For example:
@@ -52,15 +52,15 @@ controllerManager:
 ```
 
 ```bash
-helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.2" \
+helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.3" \
   --create-namespace --namespace=kueue-system \
   --values overrides.yaml
 ```
 
 You can also use the `--set` flag. For example, to enable a feature gate (e.g., `TopologyAwareScheduling`):
 
 ```bash
-helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.2" \
+helm install kueue oci://registry.k8s.io/kueue/charts/kueue --version="0.15.3" \
   --create-namespace --namespace=kueue-system \
   --set "controllerManager.featureGates[0].name=TopologyAwareScheduling" \
   --set "controllerManager.featureGates[0].enabled=true"

cmd/experimental/kueue-populator/README.md

@@ -41,7 +41,7 @@ You can also install the `kueue-populator` using the provided Helm chart.
 
 ```bash
 helm install kueue-populator oci://registry.k8s.io/kueue/charts/kueue-populator \
-  --version 0.15.2 \
+  --version 0.15.3 \
   --namespace kueue-system \
   --create-namespace \
   --wait

cmd/experimental/kueue-populator/charts/kueue-populator/Chart.yaml

@@ -2,10 +2,10 @@ apiVersion: v2
 name: kueue-populator
 description: A Helm chart for Kueue Populator setup including Kueue, LocalQueue Creator, and default resources.
 type: application
-version: 0.15.2
-appVersion: "v0.15.2"
+version: 0.15.3
+appVersion: "v0.15.3"
 dependencies:
   - name: kueue
-    version: "~0.15.2"
+    version: "~0.15.3"
     repository: "file://../../../../../charts/kueue"
     condition: kueue.enabled

cmd/experimental/kueue-populator/charts/kueue-populator/README.md

@@ -34,7 +34,7 @@ You can install the chart directly from the OCI registry:
 
 ```bash
 helm install kueue-populator oci://registry.k8s.io/kueue/charts/kueue-populator \
-  --version 0.15.2 \
+  --version 0.15.3 \
   --namespace kueue-system \
   --create-namespace \
   --wait
@@ -112,7 +112,7 @@ kueuePopulator:
 
 ```bash
 helm install kueue-populator oci://registry.k8s.io/kueue/charts/kueue-populator \
-  --version 0.15.2 \
+  --version 0.15.3 \
   --namespace kueue-system \
   --create-namespace \
   --wait \
@@ -125,7 +125,7 @@ For simple configuration you may also use the minimalistic command:
 
 ```bash
 helm install kueue-populator oci://registry.k8s.io/kueue/charts/kueue-populator \
-  --version 0.15.2 \
+  --version 0.15.3 \
   --namespace kueue-system \
   --create-namespace \
   --wait \

cmd/kueueviz/INSTALL.md

@@ -3,7 +3,7 @@
 KueueViz can be installed using `kubectl` with the following command:
 
 ```
-kubectl create -f https://github.com/kubernetes-sigs/kueue/releases/download/v0.15.2/kueueviz.yaml
+kubectl create -f https://github.com/kubernetes-sigs/kueue/releases/download/v0.15.3/kueueviz.yaml
 ```
 If you are using `kind` and that you don't have an `ingress` controller, you can use `port-forward` to 
 configure and run `KueueViz`:
@@ -23,7 +23,7 @@ by ensuring that `enableKueueViz` is set to `true`:
 
 ```
 helm upgrade --install kueue oci://registry.k8s.io/kueue/charts/kueue \
-  --version="0.15.2"
+  --version="0.15.3"
   --namespace kueue-system \
   --set enableKueueViz=true \
   --create-namespace
@@ -44,7 +44,7 @@ kind create cluster
 kind get kubeconfig > kubeconfig
 export KUBECONFIG=$PWD/kubeconfig
 helm install kueue oci://us-central1-docker.pkg.dev/k8s-staging-images/charts/kueue \
-            --version="0.15.2" --create-namespace --namespace=kueue-system
+            --version="0.15.3" --create-namespace --namespace=kueue-system
 ```
 
 ## Build