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

Helm: Support declarative definition of values files in Git separate from the helm repo

XMLWordPrintable

    • Helm: Support declarative definition of values files
    • False
    • False
    • To Do
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      Upstream Proposal :

      multiple-sources-for-applications

      Scenario:

      I would like to use values.yaml file from Git with a Helm Chart from a Helm Repository not necessarily managed by me (example the Red Hat Helm Repo ).
      Support more than one source for creating an Application.

      1. Helm chart + values from Git
      2. Proposal: Support multiple sources for an application

      Problem Statement

      Currently, Argo CD supports Applications with only a single ApplicationSource. In certain scenarios, it would be useful to support more than one source for the application. For example, consider a need to create multiple deployments of the same application and manifests but manifests can come from different sources. Today we would have to copy manifest files from one application to another.

      For example, from one of the comments on this proposal PR


      An independent support of the Helm charts and their values files. This opens a door to such highly requested scenarios like multiple deployments of the same (possibly external) Helm chart with different values files or an independent migration to a newer Helm chart version for the same applications installed in Test and Production environments.

      Creating applications from multiple sources would allow users to configure multiple services stored at various sources within the same application.

      Acceptance Criteria

      1. Users should be able to specify multiple sources to add services to the application. Argo CD should compile all the sources and reconcile each source individually for creating the application.
      2. Users should be able to specify different sources for Helm charts and values files. The Helm charts specified by the user could be available in Git or Helm repository and the value files are stored in Git. Argo CD should track changes in both the Helm charts and the value files repository and reconcile the application.
      3. Application is sync'd successfully and workloads are deployed.

      Implementation Details mentioned in the proposal

       Non-Goals

      1. Changes to UI and CLI would not be a part of this epic

       

              isequeir@redhat.com Ishita Sequeira
              shbose Shoubhik Bose
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: