-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
Product / Portfolio Work
-
-
0% To Do, 100% In Progress, 0% Done
-
False
-
-
False
-
S
-
None
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
Feature Overview (aka. Goal Summary)
The Red Hat Build of Kueue (Kueue) will need to be inspected, to this end we need to add in necessary telemetry outwith of that currently supplied by default for operators. This will address things at several levels, information relevant to the operator use itself but also information relevant to users/consumers of Kueue.
A staring point for RHOAI asks is provided here: RHOAI - Workload Orchestration Metrics.]
Note: not all the points in the linked RHOAI doc need to be addressed here, there will likely be some triage necessary to identify the items that make sense to be delivered at this level of the Kueue operator.
Goals (aka. expected user outcomes)
RHBoK additional observability is added
Requirements (aka. Acceptance Criteria):
RHBoK has additional observability
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | Both |
Classic (standalone cluster) | Yes |
Hosted control planes | Yes |
Multi node, Compact (three node), or Single node (SNO), or all | All |
Connected / Restricted Network | Both |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | x86_x64 initially |
Operator compatibility | Yes |
Backport needed (list applicable versions) | No |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | No |
Other (please specify) | n/a |
Use Cases (Optional):
Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
<your text here>
Questions to Answer (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
<your text here>
Out of Scope
High-level list of items that are out of scope. Initial completion during Refinement status.
<your text here>
Background
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
<your text here>
Customer Considerations
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.
<your text here>
Documentation Considerations
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.
<your text here>
Interoperability Considerations
Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.
<your text here>
- clones
-
OCPSTRAT-1947 RHBoK (Kueue) - operator disconnected support
-
- Closed
-
- is depended on by
-
ACM-18472 ACM Options to support RHBoK for multiKueue workloads using RHACM
-
- In Progress
-
- is related to
-
ACM-20323 Support for RHBoK Observability additions when used in RHACM
-
- New
-
- relates to
-
RFE-3175 "Access to low level HW and GPU metrics"
-
- Closed
-
-
RFE-2968 Batch scheduler in openshift
-
- Closed
-
- links to