Epic Goal

• Show Rollouts instances in the Topology View, initially as a Tech Preview.
• This Epic replaces https://issues.redhat.com/browse/GITOPS-4600 

Why is this important?

• See parent feature.  This epic will address the requirement: "Rollouts resources are visible and enriched to the same level as Deployments in Topology"
• The Rollout Manager deployment instances are currently shown in the view, but the Rollout instances are not.  This is a gap.

Scenarios

1. User creates one or more rollouts. User navigates to the Topology view and sees the nodes that represent these rollout instances.
2. User selects a rollout from the view, and more detailed information about the rollout appears
3. Here is an initial POC, showing new Rollout nodes in the Topology view. See the child stories for more details.
   

EDIT. Updated screenshot for GitOps 1.17

Other Considerations

• <Call out anything explicitly as Out of Scope?>
  • Not at this time
• <Call out internal and external dependencies?>
  • The work will be done in the current GitOps Dynamic Plugin. Any needed APIs, such as the component for the Pod ring, will be dependent upon them being available in the Dynamic Plugin SDK
• <Are there any known previous works?>
  • N/A
• <Any unanswered questions?>
  •  

Definition of Ready

• The epic has been broken down into stories.
• Stories have been scoped.
• The epic has been stack ranked.

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository / project.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.