Skip to content

Matrix Generator

The Matrix generator combines the parameters generated by two child generators, iterating through every combination of each generator's generated parameters.

By combining both generators parameters, to produce every possible combination, this allows you to gain the instrinsic properties of both generators. For example, a small subset of the many possible use cases include:

  • SCM Provider Generator + Cluster Generator: Scanning the repositories of a GitHub organization for application resources, and targeting those resources to all available clusters.
  • Git File Generator + List Generator: Providing a list of applicatations to deploy via configuration files, with optional configuration options, and deploying them to a fixed list of clusters.
  • Git Directory Generator + Cluster Decision Resource Generator: Locate application resources contained within folders of a Git repository, and deploy them to a list of clusters provided via an external custom resource.
  • And so on...

Any set of generators may be used, with the combined values of those generators inserted into the template parameters, as usual.

Example: Git Directory generator + Cluster generator

As an example, imagine that we have two clusters:

  • A staging cluster (at
  • A production cluster (at

And our application YAMLs are defined in a Git repository:

  • Argo Workflows controller (examples/git-generator-directory/cluster-addons/argo-workflows)
  • Prometheus operator (/examples/git-generator-directory/cluster-addons/prometheus-operator)

Our goal is to deploy both applications onto both clusters, and, more generally, in the future to automatically deploy new applications in the Git repository, and to new clusters defined within Argo CD, as well.

For this we will use the Matrix generator, with the Git and the Cluster as child generators:

yaml apiVersion: kind: ApplicationSet metadata: name: cluster-git spec: generators: # matrix 'parent' generator - matrix: generators: # git generator, 'child' #1 - git: repoURL: revision: HEAD directories: - path: examples/matrix/cluster-addons/* # cluster generator, 'child' #2 - clusters: selector: matchLabels: cluster template: metadata: name: '{{path.basename}}-{{name}}' spec: project: '{{metadata.labels.environment}}' source: repoURL: targetRevision: HEAD path: '{{path}}' destination: server: '{{server}}' namespace: '{{path.basename}}'

First, the Git directory generator will scan the Git repository, discovering directories under the specified path. It discovers the argo-workflows and prometheus-operator applications, and produces two corresponding sets of parameters: ```yaml - path: /examples/git-generator-directory/cluster-addons/argo-workflows path.basename: argo-workflows

  • path: /examples/git-generator-directory/cluster-addons/prometheus-operator path.basename: prometheus-operator ```

Next, the Cluster generator scans the set of clusters defined in Argo CD, finds the staging and production cluster secrets, and produce two corresponding sets of parameters: ```yaml - name: staging server:

  • name: production server: ```

Finally, the Matrix generator will combine both sets of outputs, and produce: ```yaml - name: staging server: path: /examples/git-generator-directory/cluster-addons/argo-workflows path.basename: argo-workflows

  • name: staging server: path: /examples/git-generator-directory/cluster-addons/prometheus-operator path.basename: prometheus-operator

  • name: production server: path: /examples/git-generator-directory/cluster-addons/argo-workflows path.basename: argo-workflows

  • name: production server:
    path: /examples/git-generator-directory/cluster-addons/prometheus-operator path.basename: prometheus-operator ``` (The full example can be found here.)


  1. The Matrix generator currently only supports combining the outputs of only two child generators (eg does not support generating combinations for 3 or more).
  2. You should specify only a single generator per array entry, eg this is not valid: ```yaml
  3. matrix: generators:
    • list: # (...) git: # (...) ```
    • While this will be accepted by Kubernetes API validation, the controller will report an error on generation. Each generator should be specified in a separate array element, as in the examples above.
  4. The Matrix generator does not currently support template overrides specified on child generators, eg this template will not be processed: ```yaml
  5. matrix: generators:
    • list: elements: - # (...) template: { } # Not processed ```
  6. Combination-type generators (matrix or merge) can only be nested once. For example, this will not work: ```yaml
  7. matrix: generators:
    • matrix: generators: - matrix: # This third level is invalid. generators: - list: elements: - # (...) ```