-
Epic
-
Resolution: Done
-
Major
-
ACM 2.15.0
-
Enhance multicluster SDK for VM details and actions
-
Product / Portfolio Work
-
False
-
-
False
-
Not Selected
-
In Progress
-
VIRTSTRAT-53 - ACM-CNV UI integration and multi-cluster SDK supporting VM list, VM details, VNC Console
-
VIRTSTRAT-53ACM-CNV UI integration and multi-cluster SDK supporting VM list, VM details, VNC Console
-
0% To Do, 0% In Progress, 100% Done
OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit
*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*
Epic Goal
Add features to the multicluster SDK to support the integration of the full VM details page into ACM
Why is this important?
Customers do not want users to have to switch to the console of a managed cluster and log in separately to work with the full VM details UI for VMs that are distributed across various clusters in the fleet. This epic will add multicluster versions of functions, hooks, and components
Scenarios
Other OpenShift console dynamic plugins can install the @stolostron/multicluster-sdk package and use its APIs. When ACM is available and providing a compatible implementation, the APIs can work with all clusters in the fleet.
Acceptance Criteria
- The multicluster SDK provides CRUD functions for working with Kubernetes resources on a given cluster
- Hooks are provided for checking if multicluster observability is enabled and performing Prometheus queries against it
- Multicluster equivalents for components ResourceLink and ResourceEventStream are provided
- Access review hook is provided to support multicluster RBAC checks
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions:
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue> - DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue> - DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Doc issue opened with a completed template. Separate doc issue
opened for any deprecation, removal, or any current known
issue/troubleshooting removal from the doc, if applicable. - Considerations were made for Extended Update Support (EUS)