Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-4600

Progressive Delivery in OpenShift Console's Topology View

XMLWordPrintable

    • Progressive Delivery in OpenShift Console's Topology View
    • False
    • None
    • False
    • To Do
    • SECFLOWOTL-163 - Progressive Delivery in OpenShift Console's Topology View
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • (Much of the details are TBD until the child spike is completed)
      • ...

       

      Jonathan: I converted this from a spike to a feature, based on discussions with architect/PM. The original spike can be found as a child of the epic: https://issues.redhat.com/browse/GITOPS-2339. Much of the details are TBD until the spike is completed.

      Why is this important?

      Scenarios

      1. ...

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      Open questions::

      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

              Unassigned Unassigned
              jgwest Jonathan West
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: