Course contentsShow
← Cloud and Infrastructure
Lesson 1893 of 2,98940. ArgoCDFree lesson

Multiple Source Applications

Configuring applications with multiple Git repositories or Helm chart sources.

Multiple Source Applications

You'll learn how to configure an ArgoCD Application to pull manifests from more than one Git repository or Helm source, enabling modular configuration management.

Why Multiple Sources?

In real-world scenarios, your application configuration often lives in different places: core application manifests in one repo, environment-specific values in another, and maybe a shared library chart elsewhere. ArgoCD's multiple source feature lets you combine these without manually merging them.

Think of it like assembling a meal from different grocery stores—you get produce from one, meat from another, and spices from a specialty shop. Each store (source) provides what it does best, and you combine them at deployment time.

Configuring Multiple Sources

Instead of a single source field in your Application spec, you use a sources array:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: my-multi-source-app
spec:
  project: default
  destination:
    server: https://kubernetes.default.svc
    namespace: production
  sources:
    - repoURL: https://github.com/org/helm-charts
      chart: my-app
      targetRevision: 1.0.0
    - repoURL: https://github.com/org/config-repo
      path: overlays/production
      targetRevision: main

How It Works

ArgoCD processes each source in order, merging the rendered manifests. Typically, the first source provides the base (like a Helm chart), and subsequent sources provide overrides (like Kustomize overlays or additional value files).

Common Patterns

  • Helm chart + values repo: Base chart from one repo, environment-specific values.yaml from another
  • Base manifests + overlays: Core Kubernetes YAML in one repo, Kustomize patches in another
  • Shared libraries + custom config: Reusable charts plus application-specific customizations

Key Takeaway: Multiple sources in ArgoCD Applications enable modular, composable deployments by combining manifests from different Git repositories or Helm sources into a single unified application state.