-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
Continue to refine our discover - action architectural framework
-
False
-
None
-
False
-
Not Selected
-
To Do
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
Continue to refine the pattern we can re-use for managing resources in the fleet of clusters. Some examples could be Hosted Control Planes on Multi-Cluster Engine clusters. Another is Virtual Machines on a ManagedCluster.
Why is this important?
The pattern replays for all of our core competencies. It is also the pattern for fleet management of kubernetes resources.
Scenarios
- Can I discover a resource kind and its depended resources. Example: VirtualMachine
- Can I list that resource kind across the fleet
- Can I take a specific action on that resource
- Can I take a bulk action on many similar resources
Acceptance Criteria
- Documentation of the pattern
- [SPIKE] Implementation of the pattern for a resource type (already in use for Virtual Machines)
Dependencies (internal and external)
- Discovery = Search
- Action = kubernetes api via reverse proxy, ManifestWork, and Maestro
Previous Work (Optional):
- Search discovery for Applicaitons
- Maestro
- ManifestWork, WorkAction, ManifestWorkReplicaSet
- logs and YAML via kubernetes api via reverse proxy
Open questions:
- Should we pick one action type?
Done Checklist
- Pattern is agreed upon
- Pattern is documented
- [SPIKE]Examples are available