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

POC for understanding how errata would work for bundled manifests without OLM

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • GITOPS Core Sprint 3248, GITOPS Core Sprint 3249

      Story (Required)

      As for microshift, we are using upstream argocd manifests for core components directly instead of bundling on OLM, we need to explore how errata would work with plain manifest bundle without OLM.

      Approach (Required)

      Acceptance Criteria (Mandatory)

      • Working POC for the errata setup to publish argocd core manifests.
      • Document the findings from the POC

        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

              isequeir@redhat.com Ishita Sequeira
              isequeir@redhat.com Ishita Sequeira
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: