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

Installation of GitOps operator in staging and production

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • 1.11.0
    • None
    • Testing
    • None
    • 5
    • False
    • None
    • False
    • SECFLOWOTL-91 - OpenShift GitOps on ROSA
    • GITOPS Sprint 3247, GITOPS Sprint 3248

      Story (Required)

      Ensure the operator can be successfully installed on both staging and in production environment 

      Background (Required)

      There are some challenges when if comes to installing the operator on hosted clusters. This story is intended to solve such problems 

      Out of scope

      NA

      Approach (Required)

      Follow the regular approach we use for installation of RC and a productized version. Note the challenges and come up with solution for any issues faced

      Dependencies

      You are able to get a Rosa cluster

      Acceptance Criteria (Mandatory)

      • Operator installation on a Rosa cluster is successful 
      • Acceptance tests are run (KuTTL and ArgoCD UI login)

      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

            rhn-support-vab Varsha B
            rhn-support-vab Varsha B
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: