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

Docs: Document how to use the Argo Rollouts CLI

XMLWordPrintable

    • 5
    • False
    • None
    • False
    • SECFLOWOTL-93 - Promote Rollouts to GA
    • GITOPS Service EE Sprint 257, GITOPS Service EE Sprint 258, GitOps Scarlet - Sprint 3258

      Story (Required)

      As a user of Argo Rollouts, I would like to use the Argo Rollouts CLI to manage the installed rollouts resources.

      Background (Required)

      A OpenShift GitOps user might install the Rollout resources using the GitOps approach, that is by storing all the rollouts resources in Git and allowing Argo CD to manage the deployments.

      However, after the installation, users may want to use the Argo Rollouts CLI (extent ion to kubectl plugin) to manage the rollouts. This plugin also provides a better visualization to users on how their deployment is going on.

      The installation of the rollouts extension is fairly simple and documented below.
      https://argoproj.github.io/argo-rollouts/installation/

      Out of scope

      Implementation of Argo Rollouts controller.

      Approach (Required)

      The extension is already supported by the kubectl plugin and works as expected with `oc`  as well.
      https://argoproj.github.io/argo-rollouts/installation/

      Acceptance Criteria (Mandatory)

      • Create a new Google doc in the GitOps Service EE Google Drive (for now)
      • Test them to make sure they work
      • Once the Google doc is done, let Jonathan know and he will follow up to figure out how we get that into the official OpenShift docs

      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

              jpitman63 John Pitman
              aveerama@redhat.com Abhishek Veeramalla
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: