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

Add dashboard for Rollouts

XMLWordPrintable

    • Add dashboard for Rollouts
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      New feature: With this update, an Argo Rollouts monitoring dashboard is now available from within OpenShift GitOps web console. The Argo Rollouts dashboard contains metrics related to total active Rollouts resources, number of available/desired/unavailable Replicas, and statistics on Rollouts controller performance. This dashboard can be found under Observe > Dashboards > Dashboard > GitOps / Rollouts.
      Show
      New feature: With this update, an Argo Rollouts monitoring dashboard is now available from within OpenShift GitOps web console. The Argo Rollouts dashboard contains metrics related to total active Rollouts resources, number of available/desired/unavailable Replicas, and statistics on Rollouts controller performance. This dashboard can be found under Observe > Dashboards > Dashboard > GitOps / Rollouts.
    • Feature
    • Proposed

      Epic Goal

      • Add a dashboard in the OpenShift Console to support Rollouts similar to the three existing GitOps dashboards

      Why is this important?

      • Dashboards help users manage and monitor their Rollouts effectively. 

      Scenarios

      1. View the status of all Rollouts on the cluster globally
      1. Troublehoot issues with Rollouts

      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. None

      Previous Work (Optional):

      PR created to support this:

      https://github.com/redhat-developer/gitops-operator/pull/756

      Open questions::

      1. None
      •  

      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

              jgwest Jonathan West
              gnunn@redhat.com Gerald Nunn
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: