|
| 1 | +// Module included in the following assemblies: |
| 2 | +// |
| 3 | +// * ai_workloads/kueue/release-notes.adoc |
| 4 | + |
| 5 | +:_mod-docs-content-type: REFERENCE |
| 6 | +[id="release-notes-1.2_{context}"] |
| 7 | += Release notes for {kueue-name} version 1.2 |
| 8 | + |
| 9 | +[role="_abstract"] |
| 10 | +{kueue-name} version 1.2 is a generally available release that is supported on {product-title} versions 4.18 and later. {kueue-name} version 1.2 uses link:https://kueue.sigs.k8s.io/docs/overview/[Kueue] version 0.14. |
| 11 | + |
| 12 | +[id="release-notes-1.2-new-features_{context}"] |
| 13 | +== New features and enhancements |
| 14 | + |
| 15 | +Monitoring of pending workloads:: |
| 16 | +{kueue-name} version 1.2 provides the `VisibilityOnDemand` feature to monitor the pipeline of pending jobs in the cluster queue and the local queue, and help users to estimate when their jobs will start. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/ai_workloads/red-hat-build-of-kueue#monitoring-pending-workloads.html[Monitoring pending workloads]. |
| 17 | + |
| 18 | +[id="release-notes-1.2-fixed-issues_{context}"] |
| 19 | +== Fixed issues |
| 20 | + |
| 21 | +Custom resources are not deleted properly when you uninstall {kueue-name}:: |
| 22 | +After you uninstall the {kueue-op} using the *Delete all operand instances for this operator* option in the {product-title} web console, {kueue-name} custom resources were attempted to be deleted. With this release, they are not considered for deletion. |
| 23 | ++ |
| 24 | +(link:https://issues.redhat.com/browse/OCPBUGS-62254[OCPBUGS-62254]) |
| 25 | + |
| 26 | +Documentation error in previous versions of {kueue-name}:: |
| 27 | +In link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/ai_workloads/red-hat-build-of-kueue#create-kueue-cr_install-kueue[Creating a Kueue custom resource], the optional workload types `Pod`, `Deployment`, `StatefulSet` were omitted. They are now included. |
| 28 | ++ |
| 29 | +(link:https://issues.redhat.com/browse/OCPBUGS-62877[OCPBUGS-62877]) |
| 30 | + |
| 31 | +{kueue-name} metrics were not being exposed to Prometheus from version 1.1:: |
| 32 | +Prometheus was not scraping metrics from the Operator's controller, even though the ServiceMonitor and RBAC resources were successfully created as part of the Operator installation. As a result, none of the Kueue metrics were available in the cluster monitoring stack. |
| 33 | ++ |
| 34 | +The metrics service added during the installation was configured with an incorrect port reference, causing Prometheus to fail in scraping metrics from the Kueue endpoint. The port name has been updated with the correct port name. |
| 35 | ++ |
| 36 | +(link:https://issues.redhat.com/browse/OCPBUGS-63441[OCPBUGS-63441]) |
| 37 | + |
| 38 | + |
| 39 | +[id="release-notes-1.2-known-issues_{context}"] |
| 40 | +== Known issues |
| 41 | + |
| 42 | +Reconcile jobs only in opt-in namespaces:: |
| 43 | +{product-title} allows reconciliation of `Job` resources that have the `kueue.x-k8s.io/queue-name` label, even if these resources are in namespaces which are not configured to opt in to being managed by {product-title}. This is inconsistent with the behavior for other core integrations like pods, deployments, and stateful sets, which are only reconciled if they are in namespaces which have been configured to opt in to being managed by {product-title} by adding the `kueue.openshift.io/managed=true`. |
| 44 | ++ |
| 45 | +(link:https://issues.redhat.com/browse/OCPBUGS-58205[OCPBUGS-58205]) |
| 46 | + |
| 47 | +`Kueue` CR description reads as "Not available" in the {product-title} web console:: |
| 48 | +After installing {kueue-name}, in the *Operator details* view, the description for the `Kueue` CR reads as "Not available". This issue does not affect or degrade the {kueue-name} Operator functionality. |
| 49 | ++ |
| 50 | +(link:https://issues.redhat.com/browse/OCPBUGS-62185[OCPBUGS-62185]) |
0 commit comments