Story (Required)

Match the version of Kustomize in GitOps Operator through upstream_sources.yml with the version in the Argo CD upstream tool-versions.sh file.
https://github.com/argoproj/argo-cd/blob/master/hack/tool-versions.sh

Background (Required)

We need to update the tools(Helm, Kustomize) versions up-to-date to the versions used in the upstream Argo CD to support all the features.

Out of scope

Any changes to the upstream Argo CD

Approach (Required)

There are two ways to approach this.

Approach-1: If our UBI image supports this required version of Kustomize that you are looking for, through dnf repos,  add the dnf install command in Dockerfile.
- Also remove the entry for kustomize in upstream_sources.yml
https://gitlab.cee.redhat.com/gitops-cpaas-midstream/gitops-midstream-repos/-/blob/gitops-1.8-rhel-8/upstream_sources.yaml#L36
- Remove any unwanted commands for kustomize installation in the Dockerfile
https://gitlab.cee.redhat.com/gitops-cpaas-midstream/gitops-midstream-repos/-/blob/gitops-1.8-rhel-8/distgit/containers/openshift-gitops-argocd/Dockerfile.in#L63

Approach-2: If step-1 is not feasible, we need to build the required version of Kustomize from source. We maintain a midstream repo for Helm that can be used in these cases.
https://github.com/rh-gitops-midstream/kustomize
- Update the above repo with new version by creating a new branch.

Dependencies

NA

Acceptance Criteria (Mandatory)

• Build the IIB image once your changes are merged.
• Run the IIB , create an Argo CD instance, Go to the Argo CD controller pod and verify if the Kustomize version is correct.
• Upgrade the Kustomize version in the compatibility matrix.

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