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

Write and publish a must gather component

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • 1.8.0
    • None
    • None
    • None
    • 8
    • False
    • None
    • False
    • GITOPS Sprint 228, GITOPS Sprint 229, GITOPS Sprint 230

      Story (Required)

      As a support engineer trying to diagnose a field issue I want to be able request the customer to retrieve assets enable debugging the problem by simple clicking on buttons or running a script.

      The goal of this story is to create a container image in the GitOps Operator that the customer/field engineer can remote shell in to execute the script or commands to retrieve the assets defined in GITOPS-2438

      Background (Required)

      Currently, we have to instruct customer/field engineer to gather diagnosis information. It is often too late to capture the critical information needed. Some simple steps or scripts will reduce the time to successfully gather the assets and eliminate human errors and delays.

      Out of scope

      Getting this image in CPaaS build

      Approach (Required)

      Create a simple, lightweight container image that contains scripts to grab and download diagnostics assets.  Customers can run remote shell command to execute scripts to download the assets. Take the same approach as the istio-must-gather container.

      Dependencies

      1. GITOPS-2438

      Acceptance Criteria (Mandatory)

      • A container image in GitOps Operator that includes scripts to grab and download diagnostics assets. 
      • Support this  command:
        • oc adm must-gather --image=quay.io/redhat-developer/gitops-must-gather:0.12.0

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

            rescott1 Regina Scott
            wtam_at_redhat William Tam
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: