-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
Not Selected
-
0% To Do, 100% In Progress, 0% Done
Feature Overview
The declarative nature of Kubernetes and OpenShift make it hard to understand if a cluster is performing operations. In imperative systems somebody has kicked off an action and can follow it. In declarative system, the system is deciding when to take action.
With an in-flight operations list we are introducing a feature to expose operations that are currently going on in the cluster ("ongoing or in-progress reconcilations").
Reconcilations can be viewed if an admin goes to each API endpoint individually and checks resources. But two things make this difficult:
1. All API endpoints/CRs need to be checked individually
2. Each API has it's own semantics about how in-progress/ongoing reconcillations are being signaled
This feature will surface ongoing reconcilations in a central endpoint.
Goals
- Who benefits from this feature, and how? Cluster admins will have a central point (api, cli, ui) to look at to understand what is going on in the cluster.
- What is the difference between today’s current state and a world with this feature? Today an admin has to know what to look for, has to know the api, and has to understand the api. In future the admin can look at one point and from the list knows if there is something going on or not.
Requirements
| Requirement | Notes | isMvp? |
|---|---|---|
| Central point to see ongoing reconcilations | Yes | |
| Primary focus on virtualization related resources | Yes | |
(Optional) Use Cases
How will the user interact with this feature?
Which users will use this and when will they use it?
- Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
<your text here>
Questions to answer...
Out of Scope
- High-level list of items that are out of scope. Initial completion during Refinement status.
<your text here>
**
Background, and strategic fit
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
<your text here>
Assumptions
- <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>
User Experience Considerations
Provide information that needs to be considered and planned so that the user experience will meet customer needs. These could include impacts to the UI or other areas of the user experience, as well as user research needs. Please add the 'UXD' component to this JIRA if there are User Experience considerations. Initial completion during Refinement status.
<your text here>
- is depended on by
-
CNV-45946 Task List / audit log view
-
- In Progress
-