|
6 | 6 | [id="release-notes-1.0_{context}"] |
7 | 7 | = Release notes for {kueue-name} version 1.0 |
8 | 8 |
|
9 | | -{kueue-name} version 1.0 is a generally available release that is supported on {product-title} versions 4.18 and 4.19 on the 64-bit x86 architecture. |
10 | | - |
11 | | -{kueue-name} version 1.0 uses link:https://kueue.sigs.k8s.io/docs/overview/[Kueue] version 0.11. |
| 9 | +[role="_abstract"] |
| 10 | +{kueue-name} version 1.0 is a generally available release that is supported on {product-title} versions 4.18 and 4.19 on the 64-bit x86 architecture. {kueue-name} version 1.0 uses link:https://kueue.sigs.k8s.io/docs/overview/[Kueue] version 0.11. |
12 | 11 |
|
13 | 12 | [id="release-notes-1.0-new-features_{context}"] |
14 | | -== New features in {kueue-name} version 1.0 |
15 | | - |
16 | | -The following features are supported in {kueue-name} version 1.0: |
| 13 | +== New features and enhancements |
17 | 14 |
|
18 | | -* Role-based access control (RBAC) enables you to control which types of users can create which types of {kueue-name} resources. |
| 15 | +Role-based access control (RBAC):: Role-based access control (RBAC) enables you to control which types of users can create which types of {kueue-name} resources. |
19 | 16 |
|
20 | | -* Configuring resource quotas by creating cluster queues, resource flavors, and local queues enables you to control the amount of resources used by user-submitted jobs and workloads. |
| 17 | +Configure resource quotas:: Configuring resource quotas by creating cluster queues, resource flavors, and local queues enables you to control the amount of resources used by user-submitted jobs and workloads. |
21 | 18 |
|
22 | | -* Labeling namespaces and configuring label policies enable you to control which jobs and workloads are managed by {kueue-name}. |
| 19 | +Control job and workload management:: Labeling namespaces and configuring label policies enable you to control which jobs and workloads are managed by {kueue-name}. |
23 | 20 |
|
24 | | -* Configuring cohorts, fair sharing, and gang scheduling settings enable you to share unused, borrowable resources between queues. |
| 21 | +Share borrowable resources between queues:: Configuring cohorts, fair sharing, and gang scheduling settings enable you to share unused, borrowable resources between queues. |
25 | 22 |
|
26 | 23 | [id="release-notes-1.0-known-issues_{context}"] |
27 | | -== Known issues in {kueue-name} version 1.0 |
| 24 | +== Known issues |
28 | 25 |
|
29 | | -* {kueue-name} uses the `managedJobsNamespaceSelector` configuration field, so that administrators can configure which namespaces opt in to be managed by {kueue-name}. Because namespaces must be manually configured to opt in to being managed by {kueue-name}, resources in system or third-party namespaces are not impacted or managed by {kueue-name}. |
| 26 | +Jobs in all namespaces are reconciled if they have the `kueue.x-k8s.io/queue-name` label:: {kueue-name} uses the `managedJobsNamespaceSelector` configuration field, so that administrators can configure which namespaces opt in to be managed by {kueue-name}. Because namespaces must be manually configured to opt in to being managed by {kueue-name}, resources in system or third-party namespaces are not impacted or managed by {kueue-name}. |
30 | 27 | + |
31 | | -The current behavior in {kueue-name} allows reconciliation of `Job` resources that have the `kueue.x-k8s.io/queue-name` label, even if these resources are in namespaces that are not configured to opt in to being managed by {kueue-name}. 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 that have been configured to opt in to being managed by {kueue-name}. (link:https://issues.redhat.com/browse/OCPBUGS-58205[OCPBUGS-58205]) |
| 28 | +The behavior in {kueue-name} 1.0 allows reconciliation of `Job` resources that have the `kueue.x-k8s.io/queue-name` label, even if these resources are in namespaces that are not configured to opt in to being managed by {kueue-name}. 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 that have been configured to opt in to being managed by {kueue-name}. |
| 29 | ++ |
| 30 | +(link:https://issues.redhat.com/browse/OCPBUGS-58205[OCPBUGS-58205]) |
32 | 31 |
|
33 | | -* If you try to use the {product-title} web console to create a `Kueue` custom resource (CR) by using the form view, the web console shows an error and the resource cannot be created. As a workaround, use the YAML view to create a `Kueue` CR instead. (link:https://issues.redhat.com/browse/OCPBUGS-58118[OCPBUGS-58118]) |
| 32 | +You cannot create a `Kueue` custom resource by using the {product-title} web console:: If you try to use the {product-title} web console to create a `Kueue` custom resource (CR) by using the form view, the web console shows an error and the resource cannot be created. As a workaround, use the YAML view to create a `Kueue` CR instead. |
| 33 | ++ |
| 34 | +(link:https://issues.redhat.com/browse/OCPBUGS-58118[OCPBUGS-58118]) |
0 commit comments