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

update Helm version to 3.14.3

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • 1.13.0
    • 1.13.0
    • Operator
    • 3
    • False
    • None
    • False
    • GitOps Crimson - Sprint 3257

      Story (Required)

      As a user of gitops operator, I want the most up to date helm version that argocd supports

      Background (Required)

      Argo CD 2.11-rc3 currently uses Helm 3.14.3 ([according to here|https://github.com/argoproj/argo-cd/blob/v2.11.0-rc3/hack/tool-versions.sh) |https://github.com/argoproj/argo-cd/blob/v2.11.0-rc3/hack/tool-versions.sh]).] and according to our component matrix we are currently using 3.14.0. We need to update to the most recent version of Helm. Once 2.11.0 is out, we will need to check to make sure the Helm version hasn't been updated; if it has been, then we will need to update it again accordingly. 

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Mandatory)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      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 (Inactive)
            rescott1 Regina Scott (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: